Repository navigation
Bind CI and release validation to reviewed Rust 1.97.1 - #106
Merged
Merged
Conversation
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.
Hosted floating stable now selects Rust 1.99.0, while the local release evidence used Rust 1.97.1. Current companion Clippy fails on 23 redundant
must_useattributes generated by async-trait 0.1.89 in storage traits (actual #104 CI run 36925105050). Bind CI and release validation to the reviewed 1.97.1 compiler so acceptance and publication use the same baseline. Keep the independent router Rust 1.90 MSRV lane unchanged.No warnings-denied flag, test, backend, provider, native deployment approval or current-main/tag guard is relaxed or removed. No package API/runtime/persistence/version, dependency revision or license policy changes. Rust 1.99 companion Clippy support remains an explicit follow-up in #107; this change does not claim to fix that compatibility issue.
#104 and #105 are merged predecessors. Planned .3 remains source-only, with ORM/macros 0.35.2 and router 0.5.4, at exact reviewed current main after these changes. Immutable .2 remains untouched. No .3 release or tag exists.
Validation: all local ORM count/group/projection/cross-crate acceptance on the pinned compiler is already recorded in #104; current-Rust router checks and the full 1.90 library lane pass in #105. Documentation (191 files), inventory, release-state, formatting, diff and package-release policy checks pass. The upstream toolchain action's 1.97.1 reference exists; All twelve combined checks passed at 6a8a177 in run 36929742200. The merged source 809d894 has an identical tree. Source-only .3 run 36934024517 awaits the unchanged Dastari protected-environment review; no tag/release is published yet.
Documentation impact
Explanation: release runbook records the exact compiler baseline, preserved gates and unresolved 1.99 Clippy limitation.