fix: publish as @j4k-oss/worktree-add 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/worktree-addin the j4k-oss registry, which pnpm projects can exempt fromminimumReleaseAge. Merging cuts the next patch release.The scoped name would change one runtime value, so it is pinned: the commander program name in
src/cli.tsstaysworktree-add. Without the pin,--helpwould printUsage: @j4k-oss/worktree-add. The package has no config or cache path, so nothing else readsname.The Forge CI image has git 2.39.5, which cannot start a branch in a repository with no commits (git added that in 2.42.0; reproduced on 2.41.0 and 2.42.0). On older git, worktree-add now exits with a one-line error naming the requirement, and the README states it.
The
fta-checkdev dependency becomes@j4k-oss/fta-check, with the registry pin andminimumReleaseAgeexclusion inpnpm-workspace.yaml.The rest is the j4k-align 6.7.6 sync: Forgejo workflows,
@j4k/semantic-release-forgejo, and.npm-mirror, which makes align render the GitHub workflow that will copy releases to npmjs. The repo also declaresalignModuleContract: "esm-only", because the new lint config flags the top-levelawaitin the CLI entry and the tests. npmjs stays at 2.1.0 until the mirror is set up.This PR adds
.review-enrolled, so it gets no automatic review.🤖 Generated with Claude Code