fix: publish as @j4k-oss/askpplx 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/askpplxin the j4k-oss registry, which pnpm projects can exempt fromminimumReleaseAge. Merging cuts 1.4.14.The scoped name would have changed two runtime values, so both are pinned to
askpplx:ConfprojectNameinsrc/config.ts. Without the pin, the stored API key would move from~/Library/Preferences/askpplx/to a different directory. The resolved config path is identical before and after.src/cli.ts, so--helpstill saysaskpplx.The packed tarball differs from npmjs 1.4.13 only in
package.json,README.md, and those two lines ofdist.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. npmjs stays at 1.4.13 until the mirror is set up.This PR adds
review.yml, so it gets no automatic review.🤖 Generated with Claude Code