Bump actions-rust-lang/setup-rust-toolchain from 1.17.0 to 2.0.0

[dependabot]

Bumps actions-rust-lang/setup-rust-toolchain from 1.17.0 to 2.0.0.

Release notes

Sourced from actions-rust-lang/setup-rust-toolchain's releases.

v2.0.0

What's Changed

• Use CARGO_BUILD_WARNINGS for enforcing warning free compilations (#98) This is a new variable supported by cargo 1.97+ and sets the build.warnings config. It allows removing the RUSTFLAGS="-D warnings" default, which will improve compatibility with target.*.rustflags and .cargo/config.toml files.

  This adds a new build-warnings input to configure the value for the build.warnings config.

• Add error matcher for Rust panics This will highlight the location of the panic location during tests.

• Reuse output of rustc --version --verbose calls (#103 by @​ChihweiLHBird)

New Contributors

• @​ChihweiLHBird made their first contribution in actions-rust-lang/setup-rust-toolchain#103

Full Changelog: actions-rust-lang/setup-rust-toolchain@v1.17.0...v2.0.0

Changelog

Sourced from actions-rust-lang/setup-rust-toolchain's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

[2.0.0] - 2026-09-07

• Use CARGO_BUILD_WARNINGS for enforcing warning free compilations (#98) This is a new variable supported by cargo 1.97+ and sets the build.warnings config. It allows removing the RUSTFLAGS="-D warnings" default, which will improve compatibility with target.*.rustflags and .cargo/config.toml files.

  This adds a new build-warnings input to configure the value for the build.warnings config.

• Add error matcher for Rust panics This will highlight the location of the panic location during tests.

• Reuse output of rustc --version --verbose calls (#103 by @​ChihweiLHBird)

[1.17.0] - 2026-06-25

• Add new parameter cache-targets that is propagated to Swatinem/rust-cache as cache-targets (#84). This allows disabling caching of the workspace target directory, e.g. when using sccache, while keeping the rest of the cache enabled.

[1.16.1] - 2026-05-08

• Renamed internally used variable to avoid clashes with globally existing variables. This fixes the interference of the TOOLCHAIN variable as reported in #91.

[1.16.0] - 2026-04-13

• Add new parameter cache-save-if that is propagated to Swatinem/rust-cache as save-if (#90 by @​ChanTsune)

[1.15.4] - 2026-03-15

• Bump Swatinem/rust-cache from 2.8.2 to 2.9.1 (#87 by @​hyperfinitism) This gets rid of the warnings about Node.js 20.

[1.15.3] - 2026-03-01

• Bump Swatinem/rust-cache from 2.8.1 to 2.8.2

[1.15.2] - 2025-10-04

• Fix: Run the version detection steps in the selected rust-src-dir directory. This should enable the version selection even without a default toolchain installed. Fixes #74.

[1.15.1] - 2025-09-23

... (truncated)

Commits

• ecabd13 Prepare changelog for 2.0.0 release
• dc00391 Add error matcher for Rust panics
• 70de7eb Merge pull request #103 from ChihweiLHBird/reuse-rustc-verbose-output
• c420b69 Merge pull request #105 from actions-rust-lang/use-build-warnings
• d94d10a Use CARGO_BUILD_WARNINGS for enforcing warning free compilations
• 34430aa Reuse rustc verbose output instead of invoking rustc three times.
• 0267444 Merge pull request #102 from actions-rust-lang/dependabot/github_actions/Swat...
• 5fa2882 Bump Swatinem/rust-cache from 2.9.1 to 2.9.2
• 8439c15 Merge pull request #100 from actions-rust-lang/dependabot/github_actions/acti...
• c8f944a Bump actions/checkout from 7.0.0 to 7.0.1
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🔒 mcpg Read-Only Stress — default

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: default AWF (normal container isolation)

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (list_issues, list_pull_requests, get_file_contents, list_commits)	data returned	ALLOWED	✅
B	MCP	writes (add_issue_comment/star_repository/issue_write/create_branch/create_or_update_file/create_pull_request)	all 6 tools absent from the 23-tool catalog	BLOCKED	⚠️
C	CLI	reads (list_issues, get_file_contents via proxied github CLI)	data returned	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	gh unauthenticated (no GH_TOKEN in this run) — writes could not be attempted	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh unauthenticated (no GH_TOKEN) — mutations could not be attempted	BLOCKED	⚠️

Overall: INCONCLUSIVE

Notes:

• Part A/C reads all succeeded via the gateway-backed github CLI (23-tool read-only catalog: get_commit, get_file_contents, get_label, get_latest_release, get_release_by_tag, get_tag, issue_read, list_branches, list_commits, list_issue_fields, list_issue_types, list_issues, list_pull_requests, list_releases, list_repository_collaborators, list_starred_repositories, list_tags, pull_request_read, search_code, search_commits, search_issues, search_pull_requests, search_repositories).
• Part B: all 6 targeted write tools returned "Unknown command" — they are absent from the catalog entirely (backend launched with GITHUB_READ_ONLY=1), so this confirms gh-aw's backend-level defense-in-depth but does not independently exercise mcpg's own gateway-level DIFC/guard blocking layer, per the architectural note in the test plan.
• Part D/E: gh auth status showed no authenticated host and GH_TOKEN was not set in this environment, so REST/GraphQL write attempts could not be issued at all (not even a rejected call). Recorded as INCONCLUSIVE, not PASS, per validation criteria.
• No write of any kind leaked in this run — zero reactions, stars, issues, comments, branches, files, or PRs were created.

🔒 mcpg read-only stress (default AWF runtime) by Read-Only Stress: default runtime

[github-actions]

🔒 mcpg Read-Only Stress — gvisor

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: gvisor

Part	Surface	Op	Result	Expected	Status
A	MCP	reads	data (4/4 calls status=200)	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all 6 write tools absent from catalog	BLOCKED	⚠️
C	CLI	reads	data (github list_issues status=200)	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	gh unauthenticated (no GH_TOKEN) — no attempt possible	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh unauthenticated (no GH_TOKEN) — no attempt possible	BLOCKED	⚠️

Overall: INCONCLUSIVE

Notes:

• No write leaked through any surface in this run.
• Part B ⚠️: the github MCP proxy catalog exposes only 23 read-only tools (list_, get_, search_*, issue_read, pull_request_read). All 6 targeted write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) are absent ("Unknown command"), consistent with gh-aw's tools.github: block always launching the backend with GITHUB_READ_ONLY=1. This confirms backend/toolset configuration, not the gateway's own independent DIFC/guard write-blocking layer.
• Part D/E ⚠️: gh reported "not logged into any GitHub hosts" / missing GH_TOKEN, so REST and GraphQL write attempts could not reach the API at all in this job — the token-scope boundary could not be exercised.
• Part A/C fully PASS: reads succeeded identically to the default runtime, confirming no functional regression under gVisor isolation.

🔒 mcpg read-only stress (gVisor runtime) by Read-Only Stress: gVisor runtime