fix: publish as @j4k-oss/fta-check 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/fta-checkin the j4k-oss registry, which pnpm projects can exempt fromminimumReleaseAge. Merging cuts 1.5.10.The packed tarball differs from
main's only inpackage.jsonandREADME.md;distandbinare byte-identical.The rest of the diff is the j4k-align 6.6.1 sync the Forge release needs: the Forgejo workflows,
@j4k/semantic-release-forgejo, thetsconfig.build.jsonsplit, and the oxlint and knip floors.npmjs gets
fta-check@1.5.10only once the GitHub mirror is set up; until then it stays at 1.5.9.This PR adds
review.yml, so it gets no automatic review.