Commit Graph
625 Commits
Author SHA1 Message Date
dependabot[bot] d9fed21359 chore(deps): bump github/codeql-action/autobuild from 4.38.2 to 4.39.0
Bumps [github/codeql-action/autobuild](https://github.com/github/codeql-action) from 4.38.2 to 4.39.0.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2...6f2ac81f5cd81fe351a197ba0b00d91d03cd2aee)

---
updated-dependencies:
- dependency-name: github/codeql-action/autobuild
  dependency-version: 4.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-16 10:53:25 +00:00
github-actions[bot]andeifinger 963ce8fe9e chore: update known checksums for 0.13.8 (#1131)
chore: update known checksums for 0.13.8

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-11-13 09:00:13 +01:00
Kevin Stillhammer 5e83ccf689 chore(deps): roll up Dependabot dependency updates (#1130)
## Summary
- Reproduce the remaining dependency changes from nine open Dependabot
PRs against current main, without reverting unrelated changes from older
PR branches.
- Update actions/setup-node to 7.1.0 (#1127), release-drafter to 7.10.0
(#1126), and CodeQL init/analyze/autobuild to 4.38.2 (#1116, #1115,
#1114).
- Update @types/node to 26.6.2 (#1108), undici to 8.11.0 (#1107), Biome
to 2.5.14 (#1106), and Jest to 30.5.2 (#1105).
- Align the Biome schema and regenerate affected action bundles.

## Excluded
- #1029 (TypeScript 7.0.2): all 16 test suites fail before executing
tests because ts-jest 29.4.11 expects the TypeScript compiler API and
declares a >=4.3 <7 peer range. Excluded with operator approval;
TypeScript remains at 6.0.3.
- None of the ten open Dependabot PRs were already no-ops against main.

## Validation
- npm ci --ignore-scripts
- npm run all: passed (16 suites, 179 tests; no Biome fixes)
- actionlint: passed
- uvx zizmor --offline .github/workflows: no findings
- npm audit signatures: 353 verified registry signatures, 38 verified
attestations
- Workflow all-tests-passed dependency check: passed
- git diff --check: passed

npm installation reports 30 audit vulnerabilities, matching the baseline
count; unrelated audit fixes are outside this rollup.

Refs: pi-session 01a1d01c-e089-7536-b5be-fed125cdaa18
2026-11-12 15:20:49 +01:00
yamamoto7andClaude Opus 5.5 898180d41d fix: resolve partial PEP 440 specifiers with PEP 440 semantics (#1128)
## Summary

`<=`, `==` and `>` with a partial version are valid PEP 440 specifiers,
but the resolver tries them as semver ranges first, and semver reads
them differently:

| specifier | semver (before) | PEP 440 (what uv enforces) |
|---|---|---|
| `<=0.5` | `<0.6.0`, installs 0.5.31 | `<=0.5.0`, installs 0.5.0 |
| `==0.5` | `==` is stripped and `0.5` is read as `0.5.x`, installs
0.5.31 | `==0.5.0`, installs 0.5.0 |
| `>0.5` with `resolution-strategy: lowest` | `>=0.6.0`, installs 0.6.0
| `>0.5.0`, installs 0.5.1 |

So `required-version = "<=0.5"` or `"==0.5"` in `uv.toml` /
`pyproject.toml` installs a uv that does not satisfy the project's own
`required-version`, and uv refuses to run there (`Required uv version
... does not match the running version ...`).

This is the same problem #1111 fixed for `~=`. Instead of adding more
operators to that check, specifiers that `@renovatebot/pep440` accepts
as a valid range now skip the semver evaluation, and `==` is only
stripped from a full version, so `==0.5` stays a PEP 440 pin.

Notes:

- Semver-only syntax is not valid PEP 440 and still goes through semver:
`0.4.x`, `^0.5`, `~0.5`, `>=0.4.0 <0.5.0` and a bare `0.5`.
- Inputs that are valid in both, like `>=0.4.0` from the docs, now go
through PEP 440. They mean the same in both, and the PEP 440 path uses
the same first-match lookup over the manifest.
- Full pins like `==0.9.26` still resolve as explicit versions, and
compound specifiers like `>=0.4,<=0.5` already went through PEP 440.

## Test plan

- Added cases for `<=0.9` and `==0.9` with the default strategy and
`>0.9` with `lowest` in `download-version.test.ts`. All three fail
without the change.
- `npm ci --ignore-scripts`, then `npm run build`, `npm run check` (no
fixes), `npm run package` and `npm run test:unit` on macOS with Node
24.13.0: 179 tests across 16 suites pass. The rebuilt
`dist/setup/index.cjs` only differs in the changed functions.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 15:12:48 +01:00
Kevin Stillhammer bd4d5efd86 Fix workflow tests after ubuntu-latest switch to 26.04 (#1129)
## Summary
Fix two workflow issues exposed by the `ubuntu-latest` transition to
Ubuntu 26.04, in separate commits:

- Use `npx --no-install tsc` in the workflow job dependency check
instead of relying on a globally installed TypeScript compiler, matching
https://github.com/astral-sh/ruff-action/pull/455.
- Disable caching in `test-specific-version`,
`test-version-file-version`, and `test-tool-versions-python-version`.
These jobs only verify versions or outputs and do not create a
dependency cache directory.

## Background
The cache key includes the OS version, so the runner transition caused
cache misses. Previously restored caches bypassed cache saving and hid
the missing-directory problem. On a cold cache, cleanup tried to save a
directory that these tests never created. Disabling caching makes these
non-cache tests independent of existing cache entries; dedicated cache
tests remain unchanged.

## Validation
- `npm ci --ignore-scripts` and `npm run all` using npm 11.10.0 after
the compiler fix (176 tests passed)
- Workflow TypeScript compilation and job dependency check
- `actionlint` and `uvx zizmor .github/workflows/test.yml` passed after
both changes
- `git diff --check`

Refs: pi-session 01a1cfe6-d342-70b6-a474-504b84877d9e
2026-11-12 14:45:39 +01:00
dependabot[bot] 0a73d6eb01 chore(deps): bump release-drafter/release-drafter from 7.7.0 to 7.9.0 (#1121)
Bumps
[release-drafter/release-drafter](https://github.com/release-drafter/release-drafter)
from 7.7.0 to 7.9.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/release-drafter/release-drafter/releases">release-drafter/release-drafter's
releases</a>.</em></p>
<blockquote>
<h2>v7.9.0</h2>
<h1>What's Changed</h1>
<h2>New</h2>
<ul>
<li>feat(autolabeler): sync configured pull request labels (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1787">#1787</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat(autolabeler): support multiple labels, stop rules and fallback
(<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1785">#1785</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat: expose PR labels in Drafter and Check PR outputs (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1782">#1782</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat: add resolved tag template variable (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1784">#1784</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
</ul>
<h2>Dependency Updates</h2>
<ul>
<li>ci(deps): update reviewdog/action-actionlint action to v1.77.0 (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1781">#1781</a>)
<a
href="https://github.com/apps/renovate"><code>@​renovate[bot]</code></a></li>
</ul>
<h2>Bug Fixes</h2>
<ul>
<li>fix(config): provide standard loading for the programmatic API (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1783">#1783</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>fix: skip the missing-baseline warning when <code>from</code> is set
(<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1789">#1789</a>)
<a href="https://github.com/jmeridth"><code>@​jmeridth</code></a></li>
</ul>
<h2>Maintenance</h2>
<ul>
<li>ci: dogfood Release Drafter and stage npm publishing (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1778">#1778</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>ci: lint GitHub Actions workflows with actionlint (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1780">#1780</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li>No new contributors</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/release-drafter/release-drafter/compare/v7.8.0...v7.9.0">https://github.com/release-drafter/release-drafter/compare/v7.8.0...v7.9.0</a></p>
<h2>v7.8.0</h2>
<h1>What's Changed</h1>
<h2>Token authentication change</h2>
<p>The <code>token</code> action input now takes precedence over
<code>env.GITHUB_TOKEN</code> and defaults to <code>${{ github.token
}}</code>. Pass a PAT or GitHub App token through
<code>with.token</code>, especially when publishing releases that should
trigger downstream workflows:</p>
<pre lang="yaml"><code>with:
  token: ${{ secrets.PAT }}
  publish: true
</code></pre>
<h2>New</h2>
<ul>
<li>feat: merge repeated changes with group-changes (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1725">#1725</a>)
<a
href="https://github.com/slawekjaranowski"><code>@​slawekjaranowski</code></a>,
<a href="https://github.com/claude"><code>@​claude</code></a></li>
<li>feat(facade): wire multiforge adapters (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1709">#1709</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat(adapters): add GitLab REST adapter (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1708">#1708</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat(adapters): add Gitea and Forgejo REST adapters (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1707">#1707</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
<li>feat: add config-driven check-pr validation (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1706">#1706</a>)
<a href="https://github.com/jetersen"><code>@​jetersen</code></a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/72967cdc98ddd3160f1fc3dff619de365e137dd0"><code>72967cd</code></a>
chore: release v7.9.0 (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1790">#1790</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/43cd2a9c7fdb7a2f7251be3394eabbaa641afd31"><code>43cd2a9</code></a>
feat(autolabeler): sync configured pull request labels (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1787">#1787</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/a99850f1915e19ca4688cb09fdb1aed905599e14"><code>a99850f</code></a>
feat(autolabeler): support multiple labels, stop rules and fallback (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1785">#1785</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/26b70804414cbb9f92ad61943b96089cb3e613c5"><code>26b7080</code></a>
feat: expose PR labels in Drafter and Check PR outputs (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1782">#1782</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/58b89af2fab657ccc06f1b1a8968049ac862ad37"><code>58b89af</code></a>
feat: add resolved tag template variable (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1784">#1784</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/7aa25ba4c5822e4f85a6e081a29258c05346823a"><code>7aa25ba</code></a>
fix(config): provide standard loading for the programmatic API (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1783">#1783</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/1e800128f2866500319ebd3f13ab67c4713b9f99"><code>1e80012</code></a>
fix: skip the missing-baseline warning when <code>from</code> is set (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1789">#1789</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/57f417922ac8a5cf17282aec6e7786aba69a3ee8"><code>57f4179</code></a>
ci: dogfood Release Drafter and stage npm publishing (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1778">#1778</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/75620c000f3cea11ac40a3fc917a07910bdfa677"><code>75620c0</code></a>
ci(deps): update reviewdog/action-actionlint action to v1.77.0 (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1781">#1781</a>)</li>
<li><a
href="https://github.com/release-drafter/release-drafter/commit/fb48a58bf7b2fa270433efd264ac3211839bc258"><code>fb48a58</code></a>
ci: lint GitHub Actions workflows with actionlint (<a
href="https://redirect.github.com/release-drafter/release-drafter/issues/1780">#1780</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/release-drafter/release-drafter/compare/34d80673e067bdc0c24568d3af899c216adcfaa9...72967cdc98ddd3160f1fc3dff619de365e137dd0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=release-drafter/release-drafter&package-manager=github_actions&previous-version=7.7.0&new-version=7.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-11-04 09:17:08 +01:00
William Woodruff 68ef1d76d3 Run demudhra first on macOS (#1125) 2026-11-03 13:23:25 -05:00
Zsolt Dollenstein fce2a640fd Repair cached Python directory junctions on Windows (#1122)
With `cache-python: true`, a Windows runner can report a cache hit while
extracting the cache incorrectly. When `@actions/cache`'s tar extracts
uv's minor-version junction before the patch directory it points to, it
creates a file symlink. Resolving that link later raises `[WinError 5]
Access is denied`.

This PR fixes things up after restoring the Python cache, recreating the
junction if resolving the link fails with access denied and its recorded
target is a matching, accessible CPython installation in the same
directory.

This is a temporary workaround until
https://github.com/actions/toolkit/issues/2562 gets resolved and
`@actions/cache` itself becomes resilient to these situations.

I tested this by restoring the same archive on two fresh `windows-2022`
runners. The original run passed because resolving the minor-version
link raised the expected WinError 5. With the patch, `uv sync --offline
--managed-python --no-python-downloads` created a virtual environment
whose `home` in `pyvenv.cfg` resolved to the cached CPython 3.10.22
installation. [Original
run](https://github.com/astral-sh/ruff/actions/runs/41469344610/job/125358623949#step:9:1)
· [Patched
run](https://github.com/astral-sh/ruff/actions/runs/41469344610/job/125358623835#step:10:1).
2026-11-03 19:11:16 +01:00
github-actions[bot]andeifinger a1b1886df2 chore: update known checksums for 0.13.7 (#1124)
chore: update known checksums for 0.13.7

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-11-03 09:20:52 +01:00
github-actions[bot]andeifinger 4c58170a94 docs: update version references to v10.3.3 (#1120)
Update `uses: astral-sh/setup-uv@...` references in documentation to
`68559e99cc807c1eb7e9238fd43a15bba460eec2 # v10.3.3`.

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-28 15:45:31 +01:00
Kevin StillhammerandAmp 68559e99cc Use Astral mirror for version manifests with GitHub fallback (#1119)
Amp-Thread-ID:
https://ampcode.com/threads/T-01a1822a-68da-7125-9e7d-16e038ab0840

Closes: #1118

Co-authored-by: Amp <amp@ampcode.com>
v10.3.3
2026-10-28 15:09:55 +01:00
github-actions[bot]andeifinger 0192b69518 chore: update known checksums for 0.13.6 (#1117)
chore: update known checksums for 0.13.6

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-27 11:55:43 +01:00
Kevin StillhammerandAmp 2f29784424 docs: use JSDoc for compatible release specifier comment (#1113)
Amp-Thread-ID:
https://ampcode.com/threads/T-01a17443-b5b9-703c-8877-780650eae403

Co-authored-by: Amp <amp@ampcode.com>
2026-10-26 08:49:11 +01:00
soujasKandClaude Opus 5.5 9c7332190c fix: allow whitespace in uv requirement specifiers (#1112)
## Summary

When the uv version is read from dependencies (`requirements.txt`, or
`project.dependencies` / `optional-dependencies` / `dependency-groups`
in `pyproject.toml` via `version-file`), the specifier was matched with
`/^uv([=<>~!]+\S*)/`. PEP 508 allows whitespace around operators and
after commas, and those valid forms were misread:

| dependency | before | after |
|---|---|---|
| `uv >= 0.5.0` | not found, latest uv installed | `>=0.5.0` |
| `uv == 0.11.20` | not found, latest uv installed | `==0.11.20` |
| `uv>=0.5.0, <0.6.0` | `>=0.5.0,`, fails with `No version found for
>=0.5.0,` | `>=0.5.0,<0.6.0` |

The regex now allows whitespace around operators and between
comma-separated clauses, and strips it from the result. Inputs that
worked before give the same result, including inline `--hash=` options,
trailing ` # comments`, the `\` continuation lines from `uv pip compile
--generate-hashes`, and names that only start with `uv` (`uvicorn`,
`uv-build`).

## Test plan

- Added cases for spaced operators, spaced clauses, inline `--hash` and
trailing comments. The four whitespace cases failed before the change.
- `npm run all` on Ubuntu (WSL) with Node 24.19.0: build, Biome (no
fixes), packaging, and 165 tests across 15 suites pass. The rebuilt
`dist/setup/index.cjs` only differs in the changed line.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 08:37:03 +01:00
soujasKandClaude Opus 5.5 80fbe0140c fix: resolve ~= specifiers with PEP 440 semantics (#1111)
## Summary

`~=` is the PEP 440 compatible release operator, but the resolver tries
`semver.validRange()` first, and semver accepts `~=` as a tilde range:

| specifier | semver | PEP 440 |
|---|---|---|
| `~=0.9` | `>=0.9.0 <0.10.0` | `>=0.9, ==0.*` |

So with the default `highest` strategy, `version: "~=0.9"` (or
`required-version = "~=0.9"` picked up through `version-file`) installs
the highest 0.9.x instead of the highest 0.x. The same happens with
`manifest-file`, where `tc.evaluateVersions` is semver-based.

This skips the semver evaluation for specifiers containing `~=`, so they
are only evaluated with `@renovatebot/pep440`. No semver range
legitimately uses `~=`.

Notes:

- Only a bare two-segment `~=X.Y` resolved incorrectly. `~=X.Y.Z` gives
the same result in both, and compound specifiers like `~=0.9, !=0.9.3`
were already rejected by semver and fell through to PEP 440.
- `minSatisfying` gets the same check for consistency. The lower bound
is the same under both interpretations, so `lowest` didn't produce wrong
results before.
- A single-segment `~=1` is invalid PEP 440. semver used to resolve it
to 1.x; it now fails with `No version found for ~=1`, same as other
invalid specifiers.

## Test plan

- Added tests for `~=0.9` with the default manifest and with
`manifest-file`. Both returned `0.9.26` instead of `0.10.2` before the
change.
- `npm run all` on Ubuntu (WSL) with Node 24.19.0: build, Biome (no
fixes), packaging, and 161 tests across 15 suites pass. The rebuilt
`dist/setup/index.cjs` only differs in the changed lines.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 19:39:29 +01:00
soujasKandClaude Opus 5.5 36b7b57007 fix: only report a saved cache when saving succeeded (#1110)
## Summary

The post step logs `uv cache saved with key: ...` (and `Python cache
saved with key: ...`) even when the save failed. The log in #769 shows
it right after `Warning: Failed to save: ...`:

```
Warning: Failed to save: "C:\Program failed with error: The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2
uv cache saved with key: setup-uv-2-x86_64-pc-windows-msvc-windows-11-3.12.12-pruned-...
```

`@actions/cache`'s `saveCache` doesn't throw for these failures. It logs
them and returns `-1`, and `saveCacheToKey` ignored the return value.
This now checks for `-1` before logging, which is the same check the
`actions/cache` save step uses (`if (cacheId != -1) core.info("Cache
saved with key: ...")`). `@actions/cache` already logs the reason, so
nothing else is logged on failure, and the exit code stays the same.

This only changes the log line. It doesn't address the underlying
tar/gzip failure in #769. One limitation: with the legacy (v1) cache
service, an upload that fails after the cache was reserved still returns
the reserved id, so that one case is still reported as saved. That's on
the `@actions/cache` side and affects `actions/cache` the same way.

Related to #769

## Test plan

- Added `__tests__/cache/save-cache.test.ts`. The `-1` case fails before
the change and passes after it.
- `npm run all` on Ubuntu (WSL) with Node 24.19.0 / npm 11.17.0: build,
Biome (no fixes), packaging, and all 161 tests across 16 suites pass.
The regenerated `dist/save-cache/index.cjs` only differs in the changed
lines.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 19:38:39 +01:00
github-actions[bot]andeifinger 56618cab7a docs: update version references to v10.3.2 (#1104)
Update `uses: astral-sh/setup-uv@...` references in documentation to
`07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2`.

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-22 11:25:32 +02:00
github-actions[bot]andeifinger 07a047e608 chore: update known checksums for 0.13.5 (#1103)
chore: update known checksums for 0.13.5

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
v10.3.2
2026-10-22 10:18:56 +02:00
github-actions[bot]andeifinger e1b85369e7 docs: update version references to v10.3.1 (#1102)
Update `uses: astral-sh/setup-uv@...` references in documentation to
`18d369b23da25a81e9458561248e1aafff6a70fa # v10.3.1`.

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-21 22:51:19 +02:00
Kevin Stillhammer 18d369b23d chore(deps): roll up Dependabot updates (#1101)
## Summary

Roll up the remaining dependency changes from eight open Dependabot PRs
against current `main`, without reverting newer workflow settings:

- CodeQL init, analyze, and autobuild: 4.37.7 → 4.38.1 (#1097, #1096,
#1095)
- zizmor-action: 0.6.3 → 0.6.4 (#1085)
- @biomejs/biome: 2.5.9 → 2.5.11, including its schema URL (#1075)
- @types/node: 26.2.0 → 26.4.0 (#1074)
- Jest: 30.4.2 → 30.5.0 (#1073)
- js-yaml: 5.3.0 → 5.4.1 (#1072)

All nine open Dependabot PRs had remaining dependency changes; none was
a no-op. TypeScript 7.0.2 (#1029) is intentionally deferred with
maintainer approval: ts-jest 29.4.11 requires TypeScript <7, and
applying the update caused all 15 test suites to fail before running
with `Cannot read properties of undefined (reading 'readFile')`.

The lockfile was regenerated using npm install with scripts disabled. No
runtime dependency entries changed, and repackaging produced no `dist/`
changes.

## Validation

Using Node 24.19.0 and npm 11.10.0:

- `npm ci --ignore-scripts`
- `npm run all` — passed; 15 test suites, 159 tests; Biome applied no
fixes
- `npm audit signatures` — all 353 audited packages have verified
registry signatures; 38 have verified attestations
- `actionlint .github/workflows/codeql-analysis.yml
.github/workflows/test.yml` — passed
- `uvx zizmor --no-progress --offline
.github/workflows/codeql-analysis.yml .github/workflows/test.yml` — no
findings
- `git diff --check` — passed

Refs: pi-session 01a15ec2-de1a-7557-a0bb-00369b0a4a10
v10.3.1
2026-10-21 16:17:16 +02:00
github-actions[bot]andeifinger 4ad2329c1e chore: update known checksums for 0.13.4 (#1099)
chore: update known checksums for 0.13.4

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-21 09:58:30 +02:00
github-actions[bot]andeifinger 4bc6759c82 chore: update known checksums for 0.13.2/0.13.3 (#1098)
chore: update known checksums for 0.13.2/0.13.3

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-20 08:46:37 +02:00
Danny Ward c97f06e356 fix: preserve cache error class names in save-cache bundle (#1093)
## Summary

- Preserve class names in the save-cache bundle so `@actions/cache`
error-name comparisons distinguish validation errors, benign
cache-reservation races, and finalization errors correctly.
- Add regression coverage that exercises the bundled `ValidationError`,
`ReserveCacheError`, and `FinalizeCacheError` constructors.

Fixes #1028

## Verification

- `npm run all` passed on Ubuntu 24.04 with Node 24.19.0: build, Biome,
packaging, and all 159 tests across 15 suites.
- `git diff --check` passed.

The save-cache bundle increases by about 77 KB raw (14 KB gzip) to
preserve the required names.
2026-10-15 14:57:07 +02:00
github-actions[bot]andeifinger 8ca4be000b chore: update known checksums for 0.13.1 (#1094)
chore: update known checksums for 0.13.1

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-15 08:23:05 +02:00
flange-ipb b627d85691 docs: cache-dependency-glob matches relative to the working directory (#1092)
Hello!

In #498 the behaviour of the `cache-dependency-glob` flag changed from
being relative to repository root to being relative to
`working-directory`. This is not yet documented in README.md.
[docs/caching.md](https://github.com/astral-sh/setup-uv/blob/f64d32b1cd6cc11405a74665b3dfb7bb86fea9f0/docs/caching.md#cache-dependency-glob)
already documents this behaviour correctly.
2026-10-14 15:58:35 +02:00
zaniebotandzaniebot f8c88970fc Verify npm dependency signatures before builds (#1027)
CI installs the locked npm dependency tree without running lifecycle
scripts, but it does not verify registry signatures or available
provenance attestations. Run `npm audit signatures` after installation
in both the test and checksum-update workflows, before `npm run all`
executes dependency tooling. The check follows npm's registry-signature
support and verifies attestations when present; it does not require
every dependency to publish provenance.

Related: astral-sh/ruff-action#402 adds the same signature and
provenance verification. astral-sh/setup-uv#1026 separately hardens
`npm` install defaults.

Co-authored-by: zaniebot <242828183+zaniebot@users.noreply.github.com>
2026-10-14 10:52:00 +02:00
github-actions[bot]andzanieb f64d32b1cd docs: update version references to v10.3.0 (#1090)
Update `uses: astral-sh/setup-uv@...` references in documentation to
`1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0`.

Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>
2026-10-09 23:17:16 +02:00
github-actions[bot]andzanieb 1c37ad07a6 chore: update known checksums for 0.13.0 (#1089)
chore: update known checksums for 0.13.0

Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>
v10.3.0
2026-10-09 15:33:43 -05:00
github-actions[bot]andeifinger b3c9b5fc56 chore: update known checksums for 0.12.24 (#1084)
chore: update known checksums for 0.12.24

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-09 09:36:48 +02:00
Zanie Blue b06acff4b6 Add python-arch support (#1079)
Windows ARM64 jobs may need x64 Python independently of their Python
version pin. Add `python-arch` to export `UV_PYTHON_ARCH` for subsequent
steps and include the selected architecture in the uv and managed-Python
cache keys. The input takes precedence over an inherited environment
value, and unsupported uv versions fail before environment creation.

Requires a uv release with `UV_PYTHON_ARCH` support.
2026-10-07 09:03:18 +02:00
github-actions[bot]andeifinger c84232ca4f chore: update known checksums for 0.12.23 (#1082)
chore: update known checksums for 0.12.23

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-05 08:01:54 +02:00
Charlie Marsh 51fdd265d3 Use macOS 15 runners for tests (#1081)
We move the `macos-14` test jobs to `macos-15` ahead of GitHub’s
[October 5 brownout and November 2, 2026
retirement](https://github.com/actions/runner-images/issues/13518).

We also remove the macOS 14 cache-key test case; the matrix already
covers macOS 15.
2026-10-02 15:17:20 -05:00
github-actions[bot]andeifinger a96208bed1 chore: update known checksums for 0.12.22 (#1080)
chore: update known checksums for 0.12.22

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-02 08:37:21 +02:00
github-actions[bot]andeifinger 0e3884b860 chore: update known checksums for 0.12.21 (#1078)
chore: update known checksums for 0.12.21

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-10-01 19:16:46 +02:00
github-actions[bot]andeifinger bcf05803b5 chore: update known checksums for 0.12.20 (#1076)
chore: update known checksums for 0.12.20

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-29 13:06:23 +02:00
dependabot[bot] b92a892142 chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 (#1077)
Bumps
[zizmorcore/zizmor-action](https://github.com/zizmorcore/zizmor-action)
from 0.6.2 to 0.6.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/zizmorcore/zizmor-action/releases">zizmorcore/zizmor-action's
releases</a>.</em></p>
<blockquote>
<h2>v0.6.3</h2>
<p>zizmor 1.30.0 is now the default version.</p>
<p>Release notes: <a
href="https://docs.zizmor.sh/release-notes/%5B#1300%5D(https://redirect.github.com/zizmorcore/zizmor-action/issues/1300)">zizmorcore/zizmor-action#1300</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/70fb788f84895a7701f5643d103d587e460b5c99"><code>70fb788</code></a>
Sync zizmor versions (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/162">#162</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/7999d8c8ac51dbd3bd44e6e35e7cd015b5dcdc82"><code>7999d8c</code></a>
chore(deps): bump github/codeql-action/upload-sarif from 4.37.6 to
4.37.7 in ...</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/2ae1ce9c6b7248fdfc5a4f47f3527240521f79b9"><code>2ae1ce9</code></a>
chore(deps): bump github/codeql-action/upload-sarif (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/160">#160</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/951a5eef1c3d7669c20934ceca759fdf8dbd153e"><code>951a5ee</code></a>
Skip prerelease versions in sync-zizmor-versions workflow (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/158">#158</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/79f019101434ac77d41ed24f93c6bdc8676bd355"><code>79f0191</code></a>
chore(deps): bump github/codeql-action/upload-sarif (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/156">#156</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/26a3ae6758a68e521bfe592f503410eb61b699bb"><code>26a3ae6</code></a>
sync-zizmor-versions: retry up to 5 times (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/155">#155</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/435cb31ca936c013e7509783c876307347527f14"><code>435cb31</code></a>
chore(deps): bump github/codeql-action/upload-sarif (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/151">#151</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/d6cec1055e4fad6cfafcf37200f67065ef8d7acd"><code>d6cec10</code></a>
Try the new self-referencing syntax (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/148">#148</a>)</li>
<li><a
href="https://github.com/zizmorcore/zizmor-action/commit/edd9b84a6aa802c03764a5ba7c7f627bb5974436"><code>edd9b84</code></a>
README: bump pins (<a
href="https://redirect.github.com/zizmorcore/zizmor-action/issues/150">#150</a>)</li>
<li>See full diff in <a
href="https://github.com/zizmorcore/zizmor-action/compare/3dc1ecc9bcb9e94e9b2c709687979e1298497054...70fb788f84895a7701f5643d103d587e460b5c99">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=zizmorcore/zizmor-action&package-manager=github_actions&previous-version=0.6.2&new-version=0.6.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-09-29 13:03:48 +02:00
github-actions[bot]andeifinger 227a0f6bea chore: update known checksums for 0.12.19 (#1068)
chore: update known checksums for 0.12.19

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-25 08:48:57 +02:00
github-actions[bot]andeifinger 525b679e45 chore: update known checksums for 0.12.18 (#1065)
chore: update known checksums for 0.12.18

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-23 08:08:47 +02:00
Kevin StillhammerandAmp c18668ad3c chore(deps): roll up Dependabot updates (#1059)
Co-authored-by: Amp <amp@ampcode.com>
v10.2.0
2026-09-21 08:40:50 +02:00
github-actions[bot]andeifinger ffe1476305 chore: update known checksums for 0.12.17 (#1058)
chore: update known checksums for 0.12.17

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-20 10:50:13 +02:00
github-actions[bot]andeifinger f5548c5552 chore: update known checksums for 0.12.16 (#1057)
chore: update known checksums for 0.12.16

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-18 08:48:58 +02:00
Kevin StillhammerandAmp a761a4e9af Disable automatic cache saves for merge queues (#1056)
Amp-Thread-ID:
https://ampcode.com/threads/T-01a0af68-f950-77dc-b9ae-9402987584c8

Closes: #1052

Co-authored-by: Amp <amp@ampcode.com>
2026-09-17 15:56:38 +02:00
github-actions[bot]andeifinger 3377a30666 chore: update known checksums for 0.12.15 (#1054)
chore: update known checksums for 0.12.15

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-16 08:10:10 +02:00
github-actions[bot]andeifinger dfb5f38677 chore: update known checksums for 0.12.14 (#1053)
chore: update known checksums for 0.12.14

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-15 07:41:36 +02:00
github-actions[bot]andeifinger 45c121f982 chore: update known checksums for 0.12.13 (#1045)
chore: update known checksums for 0.12.13

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-11 08:30:39 +02:00
github-actions[bot]andeifinger 8073452fd4 docs: update version references to v10.1.0 (#1044)
Update `uses: astral-sh/setup-uv@...` references in documentation to
`bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0`.

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-10 21:27:24 +02:00
Kevin Stillhammer bec219d24c chore(deps-dev): roll up Dependabot updates (#1043)
## Summary

- bump `@biomejs/biome` from 2.5.7 to 2.5.8 (#1042)
- bump `@types/node` from 26.1.2 to 26.2.0 (#1039)
- bump `esbuild` from 0.28.1 to 0.28.2 (#1040)
- update the Biome schema URL to 2.5.8

The TypeScript 7.0.2 update from #1029 is intentionally excluded:
`ts-jest` currently declares TypeScript `<7`, and the update causes all
unit suites to fail during ts-jest configuration.

## Validation

- `npm run all` (npm 11.10.0)

Refs: pi-session 01a08ca1-d3b3-7190-a02e-9a955e1b58b0
v10.1.0
2026-09-10 21:10:42 +02:00
marcel b90ec40d15 fix: respect no proxy directive (#1037)
Closes #1034
2026-09-10 20:40:43 +02:00
github-actions[bot]andeifinger 421feb646d chore: update known checksums for 0.12.12 (#1041)
chore: update known checksums for 0.12.12

Co-authored-by: eifinger <1481961+eifinger@users.noreply.github.com>
2026-09-10 08:32:00 +02:00
William Woodruff f634bf473a Expose a Python "identity" output (#1036)
https://github.com/pyca/cryptography/pull/15572#discussion_r3913508686
has the context for this: TL;DR our current `python-version` output
mirrors the "request" version exactly, which means that it's
insufficient for any downstream that needs to manage its own cache keys
(since caches shouldn't be shared across release candidates, but the `uv
python` request version doesn't include RC numbers).

The first commit here was my attempt to fix this by exposing the runtime
Python version, but this too is imprecise: the runtime version doesn't
indicate the interpreter variant (e.g. freethreading), which is also
important to capture in the cache identity.

My solution here is to expose `python-runtime-id`, which is just the
`key` of the active Python version from `uv python list
--output-format=json`.

---------

Signed-off-by: William Woodruff <william@yossarian.net>
2026-09-09 18:45:52 +02:00