Skip to content

Preserve MSRV-compatible atomic router metrics on current Rust - #105

Merged
Dastari merged 1 commit into
mainfrom
fix/router-atomic-msrv-20261001
Oct 1, 2026
Merged

Dastari merged 1 commit into
mainfrom
fix/router-atomic-msrv-20261001

Conversation

@Dastari

@Dastari Dastari commented Oct 1, 2026 •

Copy link
Copy Markdown
Owner

Current Rust deprecates AtomicUsize::fetch_update, so warnings-denied router Clippy blocks the source-only workspace release (reproduced in #104 CI router job 110580382026). Replace that private saturating decrement with the equivalent relaxed compare-exchange retry loop. Avoid requiring the replacement try_update API, preserving the declared Rust 1.90 MSRV. Existing tests cover returning gauges to baseline and saturating at zero.

Advance router to 0.5.4 rather than reuse its already-published 0.5.3 package identity. No public API, protocol, configuration, stored data, dependency revision, license policy or binary distribution change. This is a separate compiler compatibility fix; it does not expand the ORM capability PRs.

#104 is merged and this PR targets main. Source-only workspace .3 will include the exact reviewed merge of both follow-ups. .2 remains immutable. No tag or release has been published for .3.

Validation:

Documentation impact

  • Documentation updated
  • No documentation impact

Explanation: patch changelog, no-action migration notes, aligned README version and generated inventory.

@Dastari
Dastari marked this pull request as ready for review October 1, 2026 21:10
@Dastari
Dastari changed the base branch from fix/orm-release-fixture-locks-20261001 to main October 1, 2026 21:28
@Dastari
Dastari merged commit 6e478d2 into main Oct 1, 2026
11 of 12 checks passed
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.

1 participant