ci: continuous-delivery releases (single guarded bump, pin cicd @v1)#124
Merged
Conversation
Move to the ecosystem single release process (continuous delivery): - release.yml now triggers on push to `main` (+ tag push + workflow_dispatch). The shared strongo/cicd release workflow bumps from conventional commits and releases in ONE run, so the GITHUB_TOKEN-created tag no longer has to trigger a second workflow (the cause of releases silently stalling at v0.40.1 while tags climbed to v1.32.0). An explicit vX.Y.Z tag still releases that exact version. - golangci.yml sets disable-version-bumping: true so the CI workflow no longer cuts a competing tag; the release workflow is the sole bumper. Pinned to @v1 (was @main). - Pre-1.0 guard: allow_major_version_bump stays false, so the accumulated breaking (`feat!:`) commits since v0.64.2 are CAPPED to a minor bump (-> v0.65.0) rather than jumping to v1. (The orphan v1.x tags were removed.) - chocolatey/snap now run only when core actually cut a tag this run (needs.core.outputs.tag) or on an explicit tag push, so a docs-only merge doesn't try to publish an untagged commit. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HZythDmdpA3cm1pNdeirwp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves ingitdb-cli onto the ecosystem single release process (continuous delivery), and fixes the two bugs found while auditing releases.
What was broken
GITHUB_TOKEN, which by GitHub's rules can't trigger the tag-listeningrelease.yml. Tags climbed to v1.32.0; nothing published.feat(cli)!:commit had accidentally major-bumped v0.64.2 → v1.0.0 (github-tag-action treats!as major regardless of themajor_string_tokensentinel). ingitdb is pre-1.0. The 85 orphan v1.x tags (zero of them released) have been deleted; the tag line resumes at v0.64.2.What this does
release.yml: triggers on push tomain(+ tag push +workflow_dispatch). The shared strongo/cicd workflow bumps from conventional commits and releases in one run — no cross-workflow token cascade. An explicitvX.Y.Ztag still releases that exact version.golangci.yml:disable-version-bumping: true(CI only builds/lints/tests;release.ymlis the sole bumper). Pinned@v1(was@main).allow_major_version_bump: false→ the accumulated breaking commits since v0.64.2 are capped to a minor (→ v0.65.0), not a v1 jump. Cut v1.0.0 deliberately by pushing that tag.coreactually cut a tag (needs.core.outputs.tag) or on a tag push — a docs-only merge won't try to publish an untagged commit.Effect on merge
The first CD run should publish v0.65.0 — ingitdb-cli's first release since March — exercising the dormant notarize scaffold (skipped, unsigned) and the Homebrew cask for the first time.
Depends on the strongo/cicd guard (merged;
v1→ v1.9.1) and the orphan-tag cleanup (done).🤖 Generated with Claude Code