ci: align release workflows with unified tag-push trigger#35
Merged
Conversation
Both workflows now follow the same pattern: - Trigger on tag push (fw-* or cli-*) + workflow_dispatch for re-runs - Verify version in source (dist-manifest.yml / Cargo.toml) matches tag - Create release automatically if it doesn't exist, or upload assets with --clobber if it does (fixes fw-4.0.0 duplicate release error) Framework workflow gains: version verification, workflow_dispatch, idempotent release creation. CLI workflow changes: trigger moved from release:published to tag push, removing the need to manually create releases before CI runs. Updated CLAUDE.md release procedures to reflect the simplified flow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
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
2 participants
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.
Summary
workflow_dispatchfor manual re-runs, and idempotent release creation (create if missing, upload with--clobberif exists). Fixes thefw-4.0.0duplicate release error.release: publishedtopush: tags: cli-*, eliminating the need to manually create releases before CI runs. Same idempotent pattern as framework.Unified release flow (both components)
git tag <prefix>-X.Y.Z && git push origin <prefix>-X.Y.ZTest plan
fw-4.1.0tag → verify framework release is created with ZIPcli-3.0.0tag → verify CLI release is created with 4 binariesworkflow_dispatch→ verify--clobberuploads without error🤖 Generated with Claude Code