The publish job releases packages in alphabetical order, so betas depend on versions without the new code #48

Closed
opened 2026-11-15 17:11:30 +00:00 by claude-bot · 0 comments
Member

bin/publish_all.js builds 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 its workspace:* ranges are rewritten to the previous one.

Example from the run of 2026-11-15 on develop:

Published Declares Version holding the code it needs
@quatrain/backend@1.2.23-beta.1 @quatrain/core ^1.2.20, @quatrain/types ^1.2.18 core 1.2.21-beta.1, types 1.2.19-beta.1
@quatrain/backend-postgres@1.2.14-beta.1 @quatrain/core ^1.2.20 core 1.2.21-beta.1

A ^1.2.20 range does not accept 1.2.21-beta.1: a project installing the beta of backend gets a core without the code it was built against.

Expected:

  1. Packages are released in dependency order (dependencies first), so each one declares the versions released in the same run.
  2. Releases from develop (beta) may depend on beta versions; releases from main (stable) must never declare a prerelease dependency, and the job stops if one would.
`bin/publish_all.js` builds 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 its `workspace:*` ranges are rewritten to the previous one. Example from the run of 2026-11-15 on `develop`: | Published | Declares | Version holding the code it needs | |---|---|---| | `@quatrain/backend@1.2.23-beta.1` | `@quatrain/core ^1.2.20`, `@quatrain/types ^1.2.18` | `core 1.2.21-beta.1`, `types 1.2.19-beta.1` | | `@quatrain/backend-postgres@1.2.14-beta.1` | `@quatrain/core ^1.2.20` | `core 1.2.21-beta.1` | A `^1.2.20` range does not accept `1.2.21-beta.1`: a project installing the beta of `backend` gets a `core` without the code it was built against. Expected: 1. Packages are released in dependency order (dependencies first), so each one declares the versions released in the same run. 2. Releases from `develop` (beta) may depend on beta versions; releases from `main` (stable) must never declare a prerelease dependency, and the job stops if one would.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quatrain/core#48
No description provided.