ci: tag and GitHub-release each crate independently#52
Open
takaebato wants to merge 1 commit into
Open
Conversation
Enable git_tag_enable / git_release_enable at the [workspace] level and drop the
sql-insight [[package]] override, so each crate gets its own
`{{ package }}-v{{ version }}` tag (release-plz's default for a multi-package
workspace) and its own GitHub Release — instead of the library owning a single
plain `vX.Y.Z` tag while the CLI got none. Tags from before this switch keep the
old plain `vX.Y.Z` scheme and are left as-is; release-plz baselines on the
published crate, not the tag, so version bumps and changelogs are unaffected.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
✅ PR title follows the Conventional Commits spec. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #52 +/- ##
=======================================
Coverage 94.87% 94.87%
=======================================
Files 27 27
Lines 5486 5486
Branches 5486 5486
=======================================
Hits 5205 5205
Misses 203 203
Partials 78 78 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Switch from the "flagship" tagging scheme (the
sql-insightlibrary owns a single plainvX.Y.Ztag + GitHub Release; the CLI gets neither) to per-crate tags and releases — release-plz's default for a multi-package workspace.git_tag_enable/git_release_enableat the[workspace]level and drop thesql-insight[[package]]override.<crate>-vX.Y.Ztag (e.g.sql-insight-v0.4.0,sql-insight-cli-v0.3.0) and its own GitHub Release.vX.Y.Zscheme (the library's history) and are left as-is. release-plz baselines on the published crate (crates.io), not the git tag, so version bumps and changelogs are unaffected.No workflow triggers on tags and no badge/link references the
v*scheme, so nothing else needs updating. Prebuilt-binary attachment to the CLI release is out of scope here.🤖 Generated with Claude Code