The publish job releases packages in alphabetical order, so betas depend on versions without the new code #48
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#48
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.jsbuilds with Turborepo in dependency order, but releases packages in directory (alphabetical) order. A package is therefore packed before its dependencies get their new version, and itsworkspace:*ranges are rewritten to the previous one.Example from the run of 2026-11-15 on
develop:@quatrain/backend@1.2.23-beta.1@quatrain/core ^1.2.20,@quatrain/types ^1.2.18core 1.2.21-beta.1,types 1.2.19-beta.1@quatrain/backend-postgres@1.2.14-beta.1@quatrain/core ^1.2.20core 1.2.21-beta.1A
^1.2.20range does not accept1.2.21-beta.1: a project installing the beta ofbackendgets acorewithout the code it was built against.Expected:
develop(beta) may depend on beta versions; releases frommain(stable) must never declare a prerelease dependency, and the job stops if one would.