The publish job skips a beta whose version already exists on npm, so changed code is never published #46
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#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
bin/publish_all.jscomputes the next beta from the version in the repository (X.Y.Z->X.Y.(Z+1)-beta.0,-beta.N->-beta.N+1). When an earlier run published that version but its version bump never reached the repository (see #40), the next run computes the same version again, sees it on npm and prints:The changed code is not published and the job reports a success. Today
@quatrain/backend-postgres@1.2.14-beta.0on npm dates from 2026-11-14 08:34 UTC and holds neither the unique properties nor the row isolation merged later that day.Expected: when the computed beta already exists on npm, the script takes the next free beta counter for that version.