fix: publish as @j4k-oss/conventional-commit-msg from code.j4k.dev #1
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/publish-as-j4k-oss"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Moves releases to code.j4k.dev: the package becomes
@j4k-oss/conventional-commit-msgin the j4k-oss registry, which pnpm projects can exempt fromminimumReleaseAge. Merging cuts 1.0.12.The packed tarball differs from the published 1.0.11 only in
package.jsonandREADME.md;distandbinare byte-identical.The rest of the diff is the j4k-align 6.7.4 sync the Forge release needs: the Forgejo workflows,
@j4k/semantic-release-forgejo, andfta-checkrenamed to@j4k-oss/fta-checkwith the@j4k-ossregistry pin..npm-mirrormakes align render the GitHub workflow that will copy each release to npmjs.npmjs stays at 1.0.11 until the GitHub mirror is set up.
This PR adds
review.yml, so it gets no automatic review.