fix(publish): take the next free beta when the computed one is already on npm #47
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
qa:preview
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
quatrain/core!47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/46-publish-next-free-beta"
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?
Problem
bin/publish_all.jscomputes the next beta from the version in the repository. When an earlier run published that version and its bump never reached the repository (#40), the next run computes the same version, finds it on npm, skips the publication and reports a success.Result today:
@quatrain/backend-postgres@1.2.14-beta.0on npm dates from 2026-11-14 08:34 UTC. It holds neither the unique properties (#33) nor the row isolation (#44).Change
bin/betaVersion.js:nextFreeBetaVersion(candidate, publishedVersions)returns the candidate when it is free, otherwise the next free beta counter of the same base version.bin/publish_all.jslists the versions on npmjs before a beta release and uses it. A registry failure other than an unknown package stops the release instead of publishing blind.Stable releases are unchanged.
Effect on the next run on
developPackages whose code changed since their last published beta get a new one:
backend-postgresbecomes1.2.14-beta.1.As long as #40 is open, hashes and bumps still do not reach the repository, so every run on
developpublishes one more beta of each changed package. That is noise on npm, but each beta holds the current code.Checks
developandmain.Closes #46
🤖 Generated with Claude Code