Per-component tag-triggered releases - #266
Merged
Merged
Conversation
Each component publishes only when its own <package>-v<version> release tag is cut, gated via startsWith(release.tag_name, '<package>-v'). Bindings build from source and no longer depend on publish-all-crates; a new publish-crate job publishes a single crate keyed off the tag. Retire the monolithic release fanout (publish-all-crates is now manual-dispatch only) and the create-tags job. Adds RELEASING.md.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #266 +/- ##
==========================================
- Coverage 82.50% 82.47% -0.03%
==========================================
Files 95 95
Lines 26786 26786
==========================================
- Hits 22100 22092 -8
- Misses 4686 4694 +8 ☔ 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
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.
Switches releases from a single monolithic GitHub Release (which fanned out and re-published every component) to per-component releases: each component publishes only when its own
<package>-v<version>release tag is cut.How it works
rust-publish.ymlis gated onstartsWith(github.event.release.tag_name, 'gtars-<pkg>-v').gtars-python-v*→ PyPI,gtars-r-v*→ R binary,gtars-cli-v*→ crates.io + CLI binaries,gtars-wasm-v*/gtars-node-v*→ npm,gtars-<crate>-v*/gtars-v*→ crates.io.-vdelimiter keepsgtars-v*(meta crate) from colliding withgtars-core-v*etc.Changes
needs: publish-all-cratesfrom python/cli; they build from source (path deps), so there's no dependency cascade.publish-cratejob — on a release, strips-v<version>from the tag and publishes that single crate (skips pure bindings; dependencies must already be on crates.io, so cut crate releases in dependency order).publish-all-cratesis now manual-workflow_dispatchonly (emergency "republish everything"); thecreate-tagsjob (force-pushedpy-/r-shorthand tags) is removed.RELEASING.mdand a brief note in the README; also fixed a stalegtars-py→gtars-pythonreference.Normal flow: bump the component version, merge, then
releasegha release named<package>-v<version>.Verification
rust-publish.ymlYAML validated; tag→crate parsing and thegtars-vdisambiguation unit-tested locally.workflow_call/workflow_dispatch, sorust-publish.ymlstays the sole release entry point.