ci: tag each released package instead of a dated monorepo tag #36

Closed
opened 2026-11-14 11:50:08 +00:00 by claude-bot · 0 comments
Member

Context

The packages of this monorepo are versioned independently (@quatrain/core 1.2.20, @quatrain/backend 1.2.22, …). On every release from main, the CI creates one dated tag for the whole repository (v2026.11.11). That tag carries no package version, so Git cannot answer "which commit is @quatrain/backend@1.2.22?".

The rule unit SemVer & Monorepo Tagging (workflow/semver-and-monorepo-tagging.md of AGENTS.okf) makes scoped tags mandatory for multi-package monorepos: @<scope>/<package>@<version>.

Change

  • On a release from main, create one annotated tag @quatrain/<package>@<version> for each package whose version changed in the release commit.
  • Stop creating the dated tag.
  • Existing tags are left untouched.

Out of scope

  • Beta versions published from develop are not tagged: the rule tags releases on main.
  • Past releases are not tagged retroactively.

Acceptance

  • A dry run on a past release commit lists exactly the packages whose version changed in it.
  • Private packages and prerelease versions are never tagged.
  • Running the step twice creates nothing the second time.
## Context The packages of this monorepo are versioned independently (`@quatrain/core` 1.2.20, `@quatrain/backend` 1.2.22, …). On every release from `main`, the CI creates one dated tag for the whole repository (`v2026.11.11`). That tag carries no package version, so Git cannot answer "which commit is `@quatrain/backend@1.2.22`?". The rule unit *SemVer & Monorepo Tagging* (`workflow/semver-and-monorepo-tagging.md` of AGENTS.okf) makes scoped tags mandatory for multi-package monorepos: `@<scope>/<package>@<version>`. ## Change - On a release from `main`, create one annotated tag `@quatrain/<package>@<version>` for each package whose version changed in the release commit. - Stop creating the dated tag. - Existing tags are left untouched. ## Out of scope - Beta versions published from `develop` are not tagged: the rule tags releases on `main`. - Past releases are not tagged retroactively. ## Acceptance - A dry run on a past release commit lists exactly the packages whose version changed in it. - Private packages and prerelease versions are never tagged. - Running the step twice creates nothing the second time.
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#36
No description provided.