Skip to content

fix(ci): pin nightly rustfmt toolchain to nightly-2026-07-31 - #248

Merged
schell merged 1 commit into
mainfrom
chore-rustfmt-update
Oct 11, 2026
Merged

schell merged 1 commit into
mainfrom
chore-rustfmt-update

Conversation

@schell

@schell schell commented Oct 10, 2026

Copy link
Copy Markdown
Owner

Both renderling-fmt and renderling-build-shaders have been red on every PR: rustfmt's floating nightly drifted since the repo was last formatted (March 2026), and today's nightly wants dozens of comments re-wrapped.

What

  • Pin the formatting toolchain to nightly-2026-07-31 via a workflow-level RUST_NIGHTLY_TOOLCHAIN env var
  • Both CI jobs install and run the pin (rustup install $RUST_NIGHTLY_TOOLCHAIN, cargo +$RUST_NIGHTLY_TOOLCHAIN fmt -- --check)
  • The shader/linkage codegen reads the same env var (default nightly), since cargo shaders / cargo linkage format the whole project through renderling-build. Pinning CI alone would leave the shaders job resolving floating nightly
  • AGENTS.md notes the pinned toolchain

Verified locally

  • cargo +nightly-2026-07-31 fmt -- --check passes on this tree
  • Cold regen mirroring CI (remove linkage + shaders, then cargo shaders + cargo linkage): byte-identical to HEAD

After merge

Bump the pin deliberately: reformat + regenerate shaders in one "chore: nightly fmt" PR (same pattern as #225).

Floating nightly rustfmt drifted since March 2026, breaking the renderling-fmt and renderling-build-shaders jobs on every PR. Pin the formatting toolchain via RUST_NIGHTLY_TOOLCHAIN, set at workflow level and read by renderling-build's codegen (default nightly keeps local dev unchanged). The pin has to reach the codegen call: cargo shaders/linkage format the whole project through renderling-build, so pinning only the CI installs would leave the shaders job resolving the floating nightly.
@schell
schell merged commit 425c620 into main Oct 11, 2026
9 checks passed
@schell
schell deleted the chore-rustfmt-update branch October 11, 2026 00:44
@schell schell mentioned this pull request Oct 11, 2026
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