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

Merged
crapougnax merged 2 commits from feat/36-package-release-tags into develop 2026-11-14 11:53:05 +00:00
Member

Closes #36

Change

  • New script bin/tag_released_packages.js: creates one annotated tag @quatrain/<package>@<version> for each package whose version changed in the release commit.
  • The publish job runs it on main in place of the step that created the dated tag (vYYYY.MM.DD).
  • guidelines/CONTRIBUTING_AGENTS.md describes the release tags.

Private packages and prerelease versions are skipped; an existing tag is left untouched; beta versions published from develop are not tagged. Existing tags are not modified or removed.

Verified

  • Dry run on the last release commit of main (5f199642): 14 tags listed, matching the 14 version lines changed in that commit.
  • Dry run on a beta bump commit of develop: nothing to tag.
  • Real run in a throwaway clone: 14 annotated tags created; a second run creates none.

Not exercised: the step inside the CI itself. Its first real run is the next release from main.

Not included

Past releases are not tagged retroactively.

🤖 Generated with Claude Code

Closes #36 ## Change - New script `bin/tag_released_packages.js`: creates one annotated tag `@quatrain/<package>@<version>` for each package whose version changed in the release commit. - The `publish` job runs it on `main` in place of the step that created the dated tag (`vYYYY.MM.DD`). - `guidelines/CONTRIBUTING_AGENTS.md` describes the release tags. Private packages and prerelease versions are skipped; an existing tag is left untouched; beta versions published from `develop` are not tagged. Existing tags are not modified or removed. ## Verified - Dry run on the last release commit of `main` (`5f199642`): 14 tags listed, matching the 14 `version` lines changed in that commit. - Dry run on a beta bump commit of `develop`: nothing to tag. - Real run in a throwaway clone: 14 annotated tags created; a second run creates none. Not exercised: the step inside the CI itself. Its first real run is the next release from `main`. ## Not included Past releases are not tagged retroactively. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci: tag each released package instead of a dated monorepo tag (#36)
Some checks failed
Quatrain Core Sovereign CI / Monorepo Build, Tests & Quality Audit (push) Has been cancelled
Quatrain Core Sovereign CI / Publish Changed Packages to npm (push) Has been cancelled
Quatrain Core Sovereign CI / Monorepo Build, Tests & Quality Audit (pull_request) Has been cancelled
Quatrain Core Sovereign CI / Publish Changed Packages to npm (pull_request) Has been cancelled
78c390b378
Packages are versioned independently, so the dated tag created on each
release from main (v2026.11.11) named no package version. The publish
job now runs bin/tag_released_packages.js, which creates one annotated
tag @quatrain/<package>@<version> for each package whose version changed
in the release commit, as the monorepo tagging rule requires.

Private packages and prerelease versions are skipped, existing tags are
left untouched, and beta versions published from develop are not tagged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
docs: drop the dated tag from the publication guideline (#36)
Some checks failed
Quatrain Core Sovereign CI / Monorepo Build, Tests & Quality Audit (push) Successful in 5m43s
Quatrain Core Sovereign CI / Publish Changed Packages to npm (push) Has been skipped
Quatrain Core Sovereign CI / Monorepo Build, Tests & Quality Audit (pull_request) Failing after 16m48s
Quatrain Core Sovereign CI / Publish Changed Packages to npm (pull_request) Has been cancelled
64da9bfa9b
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
crapougnax merged commit 5d911a769a into develop 2026-11-14 11:53:05 +00:00
crapougnax deleted branch feat/36-package-release-tags 2026-11-14 11:53:05 +00:00
Sign in to join this conversation.
No description provided.