Skip to content

chore(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0 - #15

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/astral-sh/setup-uv-10.1.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/astral-sh/setup-uv-10.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 15, 2026

Copy link
Copy Markdown

Bumps astral-sh/setup-uv from 10.0.1 to 10.1.0.

Release notes

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

v10.1.0 馃寛 New output python-runtime-idand respect NO_PROXY

Changes

This release adds more bheind the scene security improvements and also 2 small improvements.

NO_PROXY

This action now respects no_proxy/NO_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 for details on why this can be useful.

馃悰 Bug fixes

馃殌 Enhancements

馃О Maintenance

馃摎 Documentation

猬嗭笍 Dependency updates

Commits

Dependabot compatibility score

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)

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.0.1 to 10.1.0.
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@20cfd1b...bec219d)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 15, 2026
@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 5 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 5 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • 5 security-sensitive path(s) changed

Paths:

  • .github/workflows/bug-test.lock.yml
  • .github/workflows/feature-assess.lock.yml
  • .github/workflows/publish-pypi.yml
  • .github/workflows/security.yml
  • .github/workflows/test.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CI workflow changes may ship without failure-mode evidence
  • Dependency or CI drift could surface after merge
  • 5 CI or workflow path(s) changed

Paths:

  • .github/workflows/bug-test.lock.yml
  • .github/workflows/feature-assess.lock.yml
  • .github/workflows/publish-pypi.yml
  • .github/workflows/security.yml
  • .github/workflows/test.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

Reference set readiness gaps detected (neutral)

Reference evidence present for 1/7 areas (14%) across 5 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Present .github/workflows/security.yml
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 5 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / PR Config Audit

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

Changed-config issues require attention (action_required)

Scanned 5 config file(s) present at this commit across 5 changed config path(s) and found 6 issue(s).

Changed config files:

  • .github/workflows/bug-test.lock.yml
  • .github/workflows/feature-assess.lock.yml
  • .github/workflows/publish-pypi.yml
  • .github/workflows/security.yml
  • .github/workflows/test.yml

Top findings:

  • [high] Environment variable with secret exposed (.github/workflows/bug-test.lock.yml)
  • [high] Environment variable with secret exposed (.github/workflows/bug-test.lock.yml)
  • [high] Environment variable with secret exposed (.github/workflows/bug-test.lock.yml)
  • [high] Environment variable with secret exposed (.github/workflows/feature-assess.lock.yml)
  • [high] Environment variable with secret exposed (.github/workflows/feature-assess.lock.yml)
  • [high] Environment variable with secret exposed (.github/workflows/feature-assess.lock.yml)

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / PR Harness Audit

Commit: 6afac93b0a61e05fb6939638f77e8f63b723c7d3

No harness issues detected (success)

Scanned 5 changed config file(s) and found no harness issues.

Changed config files:

  • .github/workflows/bug-test.lock.yml
  • .github/workflows/feature-assess.lock.yml
  • .github/workflows/publish-pypi.yml
  • .github/workflows/security.yml
  • .github/workflows/test.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants