[dependabot]

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

Release notes

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

v10.3.3 🌈 Use Astral mirror for version manifests with GitHub fallback

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable. (Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes

• Use Astral mirror for version manifests with GitHub fallback @​eifinger (#1119)
• fix: allow whitespace in uv requirement specifiers @​soujasK (#1112)
• fix: resolve ~= specifiers with PEP 440 semantics @​soujasK (#1111)
• fix: only report a saved cache when saving succeeded @​soujasK (#1110)

🧰 Maintenance

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

📚 Documentation

• docs: use JSDoc for compatible release specifier comment @​eifinger (#1113)
• docs: update version references to v10.3.2 @github-actions[bot] (#1104)

Commits

• 68559e9 Use Astral mirror for version manifests with GitHub fallback (#1119)
• 0192b69 chore: update known checksums for 0.13.6 (#1117)
• 2f29784 docs: use JSDoc for compatible release specifier comment (#1113)
• 9c73321 fix: allow whitespace in uv requirement specifiers (#1112)
• 80fbe01 fix: resolve ~= specifiers with PEP 440 semantics (#1111)
• 36b7b57 fix: only report a saved cache when saving succeeded (#1110)
• 56618ca docs: update version references to v10.3.2 (#1104)
• 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)

[Copilot]

🟢 Approval recommended

The workflow update bumps setup-uv to v10.3.3 while preserving checksum verification and immutable action pinning, with no active review issues identified.

No open issues 🎉

What changed in this PR

Updates the Copilot setup workflow to use astral-sh/setup-uv v10.3.3, improving version-manifest retrieval while preserving checksum verification and immutable action pinning.

Changes:

• Bumps astral-sh/setup-uv from v10.3.2 to v10.3.3.
• Updates the pinned commit SHA to the v10.3.3 release.
• Preserves the repository’s pinned-action security convention.

File	Description
.github/​workflows/​copilot-setup-steps.yml	Updates the setup-uv action used to prepare the Copilot environment.

_{Review effort: Lite (auto)}

[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 (all status=200)	ALLOWED	✅
B	MCP	writes (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request)	all 6 targets absent from the 23-tool read-only catalog exposed	BLOCKED	⚠️
C	CLI	reads (get_file_contents README.md)	data (status=200)	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	gh not authenticated (no host login) — not attempted	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh not authenticated — not attempted	BLOCKED	⚠️

Overall: INCONCLUSIVE

No write of any kind leaked on this runtime. Part A/C reads all succeeded. Part B is INCONCLUSIVE because the gateway-backed github CLI exposes only 23 read-only tools (get_, list_, search_*) — the targeted write tools never appear in the catalog, so this only confirms backend/toolset configuration (gh-aw's GITHUB_READ_ONLY=1 wrapper), not mcpg's own independent DIFC/guard write-blocking layer. Parts D/E are INCONCLUSIVE because gh is unauthenticated in this job (gh auth status → not logged into any GitHub hosts), so the REST/GraphQL token-scope boundary could not be exercised.

No FAIL, no leaked write — but methodology gap noted per Validation Criteria.

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