Repository navigation
chore: mark add-release-pipeline tasks verified after first release - #5
Merged
Merged
Conversation
Live verification of the release pipeline completed: v0.2.0 published to PyPI via the automated CI (cz bump on push to main, uv publish via trusted publishing). All 25 tasks done. Records the resolution of design Open Question #1 (default GITHUB_TOKEN tag push does not trigger a separate workflow run → publish chained as needs: bump).
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.
The release pipeline shipped and ran end-to-end. Marking the live-verification tasks complete and recording what was learned.
Outcome
main→release.ymlbumpjob rancz bump(0.1.0 → 0.2.0, MINOR) → committed the bump + pushedv0.2.0tag →publishjob (needs: bump) built the wheel+sdist and uploaded via trusted publishing (OIDC).uvx openspec-uiverified against an unrelated repo (latigo) — the documented install line now works.mrn-dk/openspec-ui, summary carries the unofficial disclaimer.Resolved design Open Question #1
The original design split
publishas a separateon: push: tagsjob. The first release run confirmed this is broken: a tag pushed by the defaultGITHUB_TOKENdoes not trigger a new workflow run. Fix:publishis now aneeds: bumpjob in the same run, gated on ataggedjob output. No stored secrets; same trusted-publisher registration (workflowrelease.yml, environmentpypi).Two fixes applied during the run
fix(ci): seed pip into the import-check venv—uv venvcreates pip-less venvs;--seedfixes the import-check.fix(release): set git identity before cz bump and chain publish to bump—cz bumpmakes the commit itself, so git identity must be configured before it runs (was in the push step, too late); plus the publish-chaining restructure above.All 25/25 tasks complete;
openspec validatepasses. Theadd-release-pipelinechange is ready to archive.OpenSpec change:
add-release-pipeline