[dependabot]

Bumps astral-sh/setup-uv from 10.3.0 to 10.3.2.

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.3.2 🌈 update known checksums for 0.13.5

Changes

🧰 Maintenance

• chore: update known checksums for 0.13.5 @github-actions[bot] (#1103)

📚 Documentation

• docs: update version references to v10.3.1 @github-actions[bot] (#1102)

v10.3.1 🌈 preserve cache error class names in save-cache bundle

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

• fix: preserve cache error class names in save-cache bundle @​dannyward630 (#1093)

🧰 Maintenance

• chore: update known checksums for 0.13.4 @github-actions[bot] (#1099)
• chore: update known checksums for 0.13.2/0.13.3 @github-actions[bot] (#1098)
• chore: update known checksums for 0.13.1 @github-actions[bot] (#1094)
• Verify npm dependency signatures before builds @​zaniebot (#1027)

📚 Documentation

• docs: cache-dependency-glob matches relative to the working directory @​flange-ipb (#1092)
• docs: update version references to v10.3.0 @github-actions[bot] (#1090)

⬆️ Dependency updates

• chore(deps): roll up Dependabot updates @​eifinger (#1101)

Commits

• 07a047e chore: update known checksums for 0.13.5 (#1103)
• e1b8536 docs: update version references to v10.3.1 (#1102)
• 18d369b chore(deps): roll up Dependabot updates (#1101)
• 4ad2329 chore: update known checksums for 0.13.4 (#1099)
• 4bc6759 chore: update known checksums for 0.13.2/0.13.3 (#1098)
• c97f06e fix: preserve cache error class names in save-cache bundle (#1093)
• 8ca4be0 chore: update known checksums for 0.13.1 (#1094)
• b627d85 docs: cache-dependency-glob matches relative to the working directory (#1092)
• f8c8897 Verify npm dependency signatures before builds (#1027)
• f64d32b docs: update version references to v10.3.0 (#1090)
• 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

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (issues/PRs/file/commits)	data returned	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all 6 targets absent from catalog (-32602 unknown tool), none leaked	BLOCKED	⚠️
C	CLI	reads (list_issues via proxied github CLI)	data returned	ALLOWED	✅
D	CLI	REST writes	gh not authenticated (401/no creds) — not attempted	BLOCKED	⚠️
E	CLI	GraphQL mutations	gh not authenticated — not attempted	BLOCKED	⚠️

Overall: INCONCLUSIVE

⚠️ Part B: all 6 targeted write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) are absent from the gh-aw tools.github: catalog entirely (backend launched with GITHUB_READ_ONLY=1), so refusal only proves backend/toolset config, not mcpg's own DIFC/guard layer. No write leaked.

⚠️ Parts D/E: gh auth status reports not logged in in this environment, so REST/GraphQL write attempts were not executable here — the token-scope boundary could not be independently exercised this run. No attempts made, no writes leaked.

No write succeeded on any surface tested. No label applied since the run is INCONCLUSIVE, not a confirmed PASS.

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