Skip to content

chore: release#233

Merged
SebastianThiebaud merged 1 commit into
mainfrom
release-plz-2026-05-23T23-18-47Z
May 24, 2026
Merged

chore: release#233
SebastianThiebaud merged 1 commit into
mainfrom
release-plz-2026-05-23T23-18-47Z

Conversation

@prismarisk-public-release
Copy link
Copy Markdown
Contributor

@prismarisk-public-release prismarisk-public-release Bot commented May 23, 2026

🤖 New release

  • tsoracle-proto: 0.2.0 -> 0.2.1
  • tsoracle-core: 0.2.0 -> 0.2.1
  • tsoracle-consensus: 0.1.5 -> 0.1.6
  • tsoracle-yieldpoint: 0.1.4 -> 0.1.5
  • tsoracle-server: 0.2.1 -> 0.2.2
  • tsoracle-client: 0.2.0 -> 0.2.1
  • tsoracle-openraft-toolkit: 0.1.5 -> 0.1.6
  • tsoracle-driver-openraft: 0.2.0 -> 0.2.1
  • tsoracle-paxos-toolkit: 0.2.0 -> 0.2.1
  • tsoracle-driver-paxos: 0.2.0 -> 0.2.1
  • tsoracle: 0.1.6 -> 0.1.7
  • tsoracle-driver-file: 0.1.5 -> 0.1.6
Changelog

tsoracle-proto

0.2.1 - 2026-05-24

Fixed

  • (proto) bundle LeaderHint epoch into a single nested EpochWire (#252) (#273)

tsoracle-core

0.2.1 - 2026-05-24

Fixed

  • (core) return NotLeader from try_prepare_window_extension off-leader (#251) (#280)
  • (core) saturate SystemClock::now_ms instead of truncating (#249) (#272)

tsoracle-consensus

0.1.6 - 2026-05-24

Added

tsoracle-yieldpoint

0.1.5 - 2026-05-24

Fixed

  • (yieldpoint) gate tokio and parking_lot behind the yieldpoints feature (#253) (#281)

Other

  • (release) version crates independently to fix release-plz resolution (#223)
  • add READMEs for the remaining published crates (#213)
  • (paxos) per-crate READMEs + driver-choice comparison (#208)

tsoracle-server

0.2.2 - 2026-05-24

Added

Fixed

  • (server) carry the fencing epoch into the NOT_LEADER hint on stepdown (#275)
  • (proto) bundle LeaderHint epoch into a single nested EpochWire (#252) (#273)
  • (server) retry fence transient errors while racing the leadership stream (#229) (#235)
  • (server) require test-fakes for fence_yieldpoint integration test (#230)

Other

  • (server) drive serve_shutdown tests through serve_with_listener (#248) (#282)

tsoracle-client

0.2.1 - 2026-05-24

Added

Fixed

  • (client) seat leader hints atomically under the monotone-forward check (#240) (#274)
  • (proto) bundle LeaderHint epoch into a single nested EpochWire (#252) (#273)
  • (client) bound the connect+RPC pair by one per-attempt deadline (#238) (#271)
  • (client) preserve status on stale-epoch hint so it surfaces NOT_LEADER (#237) (#270)
  • (client) stop clearing leader cache on unactionable NOT_LEADER (#236) (#268)

tsoracle-openraft-toolkit

0.1.6 - 2026-05-24

Fixed

  • (openraft-toolkit) fsync truncate_after and purge writes (#260) (#279)

tsoracle-driver-openraft

0.2.1 - 2026-05-24

Added

Fixed

  • (driver-openraft) validate snapshot meta.last_log_id against payload.last_applied (#276)

tsoracle-paxos-toolkit

0.2.1 - 2026-05-24

Added

Fixed

  • (paxos-toolkit) floor MemStorage append at compacted_idx after full trim (#277)

Other

  • (paxos-toolkit) gate test-fakes integration tests behind required-features (#231)

tsoracle-driver-paxos

0.2.1 - 2026-05-24

Fixed

  • (driver-paxos) gate submit_advance on a per-call barrier nonce (#256) (#278)
  • (driver-paxos) mint a fresh apply-shutdown Notify per start (#232)

tsoracle

0.1.7 - 2026-05-24

Fixed

  • (bin) handle SIGTERM as a graceful-shutdown trigger (#245) (#269)

tsoracle-driver-file

0.1.6 - 2026-05-24

Other

  • updated the following local packages: tsoracle-core, tsoracle-consensus


This PR was generated with release-plz.

@prismarisk-public-release prismarisk-public-release Bot force-pushed the release-plz-2026-05-23T23-18-47Z branch from a63fec1 to 217d715 Compare May 23, 2026 23:19
@coveralls
Copy link
Copy Markdown

coveralls commented May 23, 2026

Coverage Report for CI Build 26350892285

Coverage increased (+0.02%) to 94.79%

Details

  • Coverage increased (+0.02%) from the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • 6 coverage regressions across 2 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

6 previously-covered lines in 2 files lost coverage.

File Lines Losing Coverage Coverage
crates/tsoracle-driver-paxos/src/state_machine.rs 4 97.39%
benchmarks/stress/src/topology/paxos.rs 2 84.37%

Coverage Stats

Coverage Status
Relevant Lines: 11209
Covered Lines: 10625
Line Coverage: 94.79%
Coverage Strength: 477240.71 hits per line

💛 - Coveralls

@prismarisk-public-release prismarisk-public-release Bot force-pushed the release-plz-2026-05-23T23-18-47Z branch 2 times, most recently from 691d5e8 to 1f016de Compare May 23, 2026 23:51
@prismarisk-public-release prismarisk-public-release Bot force-pushed the release-plz-2026-05-23T23-18-47Z branch 13 times, most recently from ba9c740 to e461479 Compare May 24, 2026 03:25
@prismarisk-public-release prismarisk-public-release Bot force-pushed the release-plz-2026-05-23T23-18-47Z branch 2 times, most recently from bbcb38b to 1f2dbe5 Compare May 24, 2026 03:33
@prismarisk-public-release prismarisk-public-release Bot force-pushed the release-plz-2026-05-23T23-18-47Z branch from 1f2dbe5 to bed6cd5 Compare May 24, 2026 03:36
@SebastianThiebaud SebastianThiebaud merged commit 1b50abb into main May 24, 2026
22 checks passed
@SebastianThiebaud SebastianThiebaud deleted the release-plz-2026-05-23T23-18-47Z branch May 24, 2026 03:44
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants