fix: publish as @j4k-oss/worktree-remove 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-removein the j4k-oss registry, which pnpm projects can exempt fromminimumReleaseAge. Merging cuts 1.4.11.The only runtime use of the package name was the CLI name (
.name(packageJson.name)insrc/cli.ts), which would have printedUsage: @j4k-oss/worktree-remove. It is now the literalworktree-remove. The package has no config, cache or user-agent use of its name.The packed tarball differs from the published 1.4.10 only in
package.json,README.mdanddist/cli.js(plus its map), where the CLI name is pinned.The rest of the diff is the j4k-align 6.7.6 sync: the Forgejo workflows and
@j4k/semantic-release-forgejo.fta-checkwas already@j4k-oss/fta-check..npm-mirrormakes align render the GitHub workflow that will copy each release to npmjs, which stays at 1.4.10 until the mirror exists.This PR adds
review.yml, so it gets no automatic review.🤖 Generated with Claude Code