Repository navigation
Bump astral-sh/setup-uv from 10.2.0 to 10.3.0 - #15111
Conversation
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.2.0 to 10.3.0. - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@c18668a...1c37ad0) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: 10.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
🔒 mcpg Read-Only Stress — defaultSurface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Overall: INCONCLUSIVE No write leaked on any surface. Part A/C reads confirmed fully functional. Part B could not confirm gateway-level (vs. backend-config) write blocking because the GitHub MCP tool catalog exposed only 23 read-only tools (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) — none of the targeted write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) were present, so no call-time refusal could be exercised. Parts D/E could not run because
|
Bumps astral-sh/setup-uv from 10.2.0 to 10.3.0.
Release notes
Sourced from astral-sh/setup-uv's releases.
Commits
1c37ad0chore: update known checksums for 0.13.0 (#1089)b3c9b5fchore: update known checksums for 0.12.24 (#1084)b06acffAddpython-archsupport (#1079)c84232cchore: update known checksums for 0.12.23 (#1082)51fdd26Use macOS 15 runners for tests (#1081)a96208bchore: update known checksums for 0.12.22 (#1080)0e3884bchore: update known checksums for 0.12.21 (#1078)bcf0580chore: update known checksums for 0.12.20 (#1076)b92a892chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 (#1077)227a0f6chore: update known checksums for 0.12.19 (#1068)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)