Repository navigation
chore: nightly fmt - #249
Merged
Merged
Conversation
Bump RUST_NIGHTLY_TOOLCHAIN to nightly-2026-10-10 and absorb the rustfmt drift repo-wide (32 files, comment re-wraps). Regenerated shaders and linkage with the new pin. Same pattern as #225.
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
1 participant
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.
Bump the pinned fmt toolchain
nightly-2026-07-31→nightly-2026-10-10and absorb the rustfmt drift in one mechanical pass (same pattern as #225).What
RUST_NIGHTLY_TOOLCHAIN: nightly-2026-10-10inpush.yaml;AGENTS.mdnote updatedcargo +nightly-2026-10-10 fmt: 32 files, comment re-wraps (the drift that broke CI on every PR before fix(ci): pin nightly rustfmt toolchain to nightly-2026-07-31 #248)