Repository navigation
Chore(deps): bump rust-toolchain from nightly-2026-03-26 to nightly-2026-10-22 - #790
dependabot[bot] wants to merge 12 commits into
Conversation
Bumps [rust-toolchain](https://github.com/rust-lang/rust) from nightly-2026-03-26 to nightly-2026-10-22. - [Release notes](https://github.com/rust-lang/rust/releases) - [Changelog](https://github.com/rust-lang/rust/blob/main/RELEASES.md) - [Commits](https://github.com/rust-lang/rust/commits) --- updated-dependencies: - dependency-name: rust-toolchain dependency-version: nightly-2026-10-22 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
@coderabbitai The only comment from you on this PR is the 08:44Z "Review skipped: Bot user detected" notice, so there are no findings or pre-merge table to check against yet. The head is now 014208f, which adds the compiler-migration fixes (try_update, lint fixes, refreshed trybuild snapshots, spelling allowance). CI at this head passes lint, spelling, markdown and all 1181 tests; the only red step is the coverage ratchet (87.8% against an 89.0% baseline), which the maintainer has explicitly overridden for this PR. Please review head 014208f and say whether any ❌ (Error) pre-merge check rows or open findings remain. |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
gh pr view 790 --repo leynos/wireframe --json headRefOid,baseRefOid,files,statusCheckRollup,reviews,comments
gh api graphql -f query='query { repository(owner:"leynos",name:"wireframe") { pullRequest(number:790) { reviewThreads(first:100) { nodes { isResolved isOutdated comments(first:20) { nodes { author { login } body url } } } pageInfo { hasNextPage endCursor } } } } }'
git rev-parse HEAD
git diff --stat "$(gh pr view 790 --repo leynos/wireframe --json baseRefOid --jq .baseRefOid)" HEAD
fd -H -t f '^(AGENTS\.md|\.coderabbit\.ya?ml)$' .Length of output: 13353 🏁 Script executed: #!/bin/bash
set -euo pipefail
cat AGENTS.md
git diff --no-ext-diff 50656d9c67ba2996eeafdcb4f0403937adc2f6d2 HEAD
gh api repos/leynos/wireframe/actions/jobs/119896934854 --jq '{head_sha,conclusion,steps:[.steps[] | {name,conclusion}]}'
gh run view 39799802018 --repo leynos/wireframe --log-failed | tail -n 100Length of output: 60488 🏁 Script executed: #!/bin/bash
set -euo pipefail
ast-grep outline examples/resp_codec_impl/encode.rs --items all
sed -n '1,180p' examples/resp_codec_impl/encode.rs
rg -n -C3 'digits_len_i64|encoded_len|RespFrame::Integer' examples/resp_codec_impl
gh run view 39799802018 --repo leynos/wireframe --log-failed | grep -Ei '1181|test result:|coverage|ratchet|89\.0|87\.8|##\[error\]' | tail -n 55
sed -n '1,110p' docs/contents.md
sed -n '1,100p' docs/repository-layout.mdLength of output: 28641
You are interacting with an AI system. |
Bumps the pinned toolchain from nightly-2026-03-26 to nightly-2026-10-22 and carries the compatibility fixes it needs: try_update in place of fetch_update, lint fixes, signed digit counting by magnitude in the RESP example with tests, refreshed trybuild snapshots, Cranelift provisioning and guide references, and a new coverage baseline path (.coverage-baseline-v2.rust at 87.8%, toolchain bump only; tests unchanged). Supersedes #790; Part of DF12-110
|
Superseded by #794, which carries the same bump plus the fixes it needs. Closing. |
Pull request was closed
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps rust-toolchain from nightly-2026-03-26 to nightly-2026-10-22.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)