chore: release#233
Merged
Merged
Conversation
a63fec1 to
217d715
Compare
Coverage Report for CI Build 26350892285Coverage increased (+0.02%) to 94.79%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions6 previously-covered lines in 2 files lost coverage.
Coverage Stats
💛 - Coveralls |
691d5e8 to
1f016de
Compare
ba9c740 to
e461479
Compare
SebastianThiebaud
previously approved these changes
May 24, 2026
bbcb38b
bbcb38b to
1f2dbe5
Compare
1f2dbe5 to
bed6cd5
Compare
SebastianThiebaud
added a commit
that referenced
this pull request
May 24, 2026
* fix(proto): bump to 0.2.2 to republish the lifted leader-hint API The published tsoracle-proto 0.2.1 (from release #233) predates the leader-hint lift in #295, which added LEADER_HINT_TRAILER_KEY, LeaderHintLookup, and decode_leader_hint to v1 under a refactor: prefix. Because crates version independently and release_commits gates releases to feat/fix/perf, that change never bumped proto's version — so the crates.io 0.2.1 lacks those symbols. tsoracle-server 0.2.3 already uses them, so cargo publish --verify built the server tarball with the path dep stripped, resolved tsoracle-proto ^0.2.1 to the stale registry 0.2.1, and failed to compile (E0432/E0425), aborting the release. Bumping to 0.2.2 (patch: additive, non-breaking; all consumers pin ^0.2.1 so they resolve to it with no cascade) gets a proto containing the symbols published ahead of the dependent crates. * docs(contributing): require feat/fix for library API additions, not refactor Document the release-mechanics trap behind the proto 0.2.2 fix: adding public API to a library crate is user-visible to dependent crates even when the gRPC wire contract (the v1 proto package) is unchanged, so it must use feat:/fix: rather than refactor:, which does not trigger a release. Also correct the stale "version.workspace = true / lockstep" claim — crates have versioned independently since #223 — and spell out the release_commits prefix filter.
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.
🤖 New release
tsoracle-proto: 0.2.0 -> 0.2.1tsoracle-core: 0.2.0 -> 0.2.1tsoracle-consensus: 0.1.5 -> 0.1.6tsoracle-yieldpoint: 0.1.4 -> 0.1.5tsoracle-server: 0.2.1 -> 0.2.2tsoracle-client: 0.2.0 -> 0.2.1tsoracle-openraft-toolkit: 0.1.5 -> 0.1.6tsoracle-driver-openraft: 0.2.0 -> 0.2.1tsoracle-paxos-toolkit: 0.2.0 -> 0.2.1tsoracle-driver-paxos: 0.2.0 -> 0.2.1tsoracle: 0.1.6 -> 0.1.7tsoracle-driver-file: 0.1.5 -> 0.1.6Changelog
tsoracle-prototsoracle-coretsoracle-consensustsoracle-yieldpointtsoracle-servertsoracle-clienttsoracle-openraft-toolkittsoracle-driver-openrafttsoracle-paxos-toolkittsoracle-driver-paxostsoracletsoracle-driver-fileThis PR was generated with release-plz.