mirror of
https://github.com/max-sixty/worktrunk.git
synced 2026-11-22 02:53:04 +08:00
codex/plugin-removal-interruption
513
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
45d9b4e842 |
Run Worktrunk Tend workflows with Codex on gpt-6-sol (#4240)
Switch Worktrunk's Tend agent workflows to Codex on `gpt-6-sol`, generated with Tend 0.3.14. Mackup's existing account rotator owns subscription refresh (`codex.auth_refresh: false`) and publishes access-only `CODEX_AUTH_JSON` plus `CODEX_ACCOUNT`. This removes the proposed hosted refresh workflow and its separate login/PAT requirement. The unused hosted-refresh PAT secret has been removed. Validation: `actionlint` and the complete branch whitespace check pass. An independent code review found no issues. GitHub CI, including Codecov, passes at `8e842331aa0f29949579050551dd2d0b67fb04b1`, and worktrunk-bot approved that exact commit. A real Codex 0.160.0 request to `gpt-6-sol` succeeded with an access-only credential derived from a saved login selected by Mackup's allocator. All 5,388 Rust tests passed (one skipped), along with documentation checks and the final full pre-commit run. Cutover requires maintainer merge authorization. Mackup reads ownership from the default branch and the `tend` environment admits only main, so credential publication and a hosted Codex run follow the merge. After landing, run the allocator, verify the published account and secret timestamp, rerun `tend check`, and validate a hosted agent run; retry any agent job that starts before publication. Current `tend check` passes every check except the missing Codex consumer credential. This supersedes the earlier dedicated-login premerge condition; hosted operation is not yet validated. > _This was written by Codex on behalf of max-sixty_ --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> Co-authored-by: Codex <noreply@openai.com> |
||
|
|
aa828a3716 |
chore: bump taiki-e/install-action from 2.87.27 to 2.87.28 (#4475)
> _This was written by Codex on behalf of max-sixty_ |
||
|
|
0149f79e10 |
chore: update tend workflows (0.3.13 → 0.3.14) (#4478)
> _This was written by Codex on behalf of max-sixty_ |
||
|
|
4227ba4627 |
chore: bump jdx/packslip from 1.6.0 to 1.7.0 (#4473)
Bumps [jdx/packslip](https://github.com/jdx/packslip) from 1.6.0 to 1.7.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/releases">jdx/packslip's releases</a>.</em></p> <blockquote> <h2>v1.7.0: Verified artifact list in <code>verify --json</code>, and support for releases signed by reusable workflows</h2> <p><code>packslip verify --json</code> now lists every artifact in the verified release, and its output has a published schema. packslip also now accepts releases signed through a reusable workflow that lives in another repository, both in the CLI and in the <code>jdx/packslip</code> Action. The packslip format is unchanged and remains version 1.</p> <h2>Added</h2> <ul> <li><strong><code>packslip verify --json</code> lists the verified artifacts.</strong> The report has a new <code>artifacts</code> array taken from the verified statement. Each entry includes the signed <code>sha256</code> and the statement's fields for that artifact (<code>name</code>, <code>size</code>, <code>url</code>, <code>format</code>, <code>os</code>, <code>arch</code>, <code>libc</code>, <code>variant</code>, <code>bin</code>, <code>requires</code>, <code>provenance</code>, <code>extensions</code>), and fields that aren't set are left out. Before, tooling had to follow <code>verify</code> with <code>packslip show</code>, which doesn't verify, to find out which file to fetch. Now one command checks the bundle and tells you what to stage. Nothing is downloaded or installed. The list is the same whether or not you pass <code>--artifact</code>, and <code>checked_artifacts</code> still records which files were hashed. Existing fields haven't changed. (<a href="https://redirect.github.com/jdx/packslip/issues/213">#213</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <pre lang="sh"><code>packslip verify packslip.sigstore.json --pin ps1_... --json \ | jq -r '.artifacts[] | select(.os == "linux" and .arch == "x86_64") | "\(.name) \(.sha256)"' </code></pre> </li> <li><strong>Published schema for the verify report.</strong> The schema is published on packslip.dev as <code>schema/verify-report-v1.json</code>, and <code>packslip schema --report</code> prints it. Within version 1 of the report, fields may be added but are never removed, renamed, or redefined. Library users get <code>packslip::VerifyReport</code>, <code>packslip::VerifiedArtifact</code>, and <code>packslip::verify_report_schema()</code> (behind the <code>schema</code> feature). (<a href="https://redirect.github.com/jdx/packslip/issues/213">#213</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> <li><strong>New <code>packslip verify --source-repository <url></code> flag.</strong> It requires the signing certificate's source repository to be <code><url></code> and to match the project named in the statement. It must be used together with <code>--issuer <issuer></code> (for GitHub Actions, the GitHub Actions OIDC token issuer). It can't be combined with <code>--identity</code>, <code>--identity-prefix</code>, or <code>--pubkey</code>. Without the flag, <code>verify</code> works as before. (<a href="https://redirect.github.com/jdx/packslip/issues/227">#227</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> <li><strong>New documentation:</strong> a guide to verify-only use with private hosts, mirrors, and air-gapped copies (<a href="https://redirect.github.com/jdx/packslip/issues/214">#214</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>), and a recipe that takes a multi-platform release from <code>packslip create</code> through <code>packslip verify</code> (<a href="https://redirect.github.com/jdx/packslip/issues/215">#215</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>).</li> </ul> <h2>Fixed</h2> <ul> <li><strong>Releases signed through another repository's reusable workflow can now be verified and installed.</strong> Before, a project that signed through a shared workflow, such as <code>suzuki-shunsuke/go-release-workflow</code>, failed with an "expected an identity starting with" error that named the project's own repository. Forge installs now verify under the forge's issuer alone and then check that the certificate's source repository is the project's own. A certificate with no source repository still has to come from a workflow of the project. The Action's "Verify what was written" step now uses <code>--source-repository</code>, and falls back to the old identity-prefix check when the CLI from <code>packslip-version</code> or <code>packslip-path</code> is too old to have the flag. The source repository comes from the same OIDC token as the signer identity, so another repository can't forge it. (<a href="https://redirect.github.com/jdx/packslip/issues/227">#227</a>, fixes <a href="https://redirect.github.com/jdx/packslip/issues/226">#226</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <ul> <li>Switching between a workflow in the project's own repository and a shared one counts as a changed signer, even when the workflow path is the same. A person has to approve it once.</li> <li>Release lists that go through <code>jdx/packslip/releases</code> still pin an identity prefix, so they can't be signed by another repository's reusable workflow yet.</li> </ul> </li> </ul> <h2>Changed</h2> <ul> <li><strong>Bundles whose DSSE envelope has more than one signature are now rejected.</strong> packslip now uses version 0.13 and later of the sigstore crates, which reject these bundles when reading them. Before, such a bundle was accepted if any one of its signatures matched. packslip only ever writes one signature, so bundles produced by packslip aren't affected. (<a href="https://redirect.github.com/jdx/packslip/issues/211">#211</a>, <a href="https://redirect.github.com/jdx/packslip/issues/218">#218</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jdx/packslip/compare/v1.6.0...v1.7.0">https://github.com/jdx/packslip/compare/v1.6.0...v1.7.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/blob/main/CHANGELOG.md">jdx/packslip's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2><a href="https://github.com/jdx/packslip/compare/v1.6.0..v1.7.0">1.7.0</a> - 2026-10-11</h2> <h3>🚀 Features</h3> <ul> <li><strong>(verify)</strong> list verified artifacts in --json and publish the report schema by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/213">#213</a></li> </ul> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(verify)</strong> accept releases signed through another repository's reusable workflow by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/227">#227</a></li> </ul> <h3>⚡ Performance</h3> <ul> <li>reduce development debug info by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/200">#200</a></li> </ul> <h3>🔍 Other Changes</h3> <ul> <li><strong>(ci)</strong> lint workflows with jactionlint by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/221">#221</a></li> <li><strong>(ci)</strong> switch to jactionlint v2 and drop zizmor by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/225">#225</a></li> </ul> <h3>📦️ Dependency Updates</h3> <ul> <li>lock file maintenance by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/198">#198</a></li> <li>pin fedora docker tag to 43b29f6 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/201">#201</a></li> <li>update dependency hugo to v0.167.0 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/203">#203</a></li> <li>update rust crate usage_rs to v6.12.1 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/210">#210</a></li> <li>update sigstore crates to 0.13 by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/211">#211</a></li> <li>update dependency usage to latest by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/212">#212</a></li> <li>update sigstore crates to 0.14 by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/218">#218</a></li> <li>update rust crate usage_rs to v7 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/224">#224</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.5.1..v1.6.0">1.6.0</a> - 2026-10-05</h2> <h3>🚀 Features</h3> <ul> <li><strong>(action)</strong> lock released CLI archive digests by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/194">#194</a></li> </ul> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(action)</strong> pin candidate archives before the shared release tag by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/195">#195</a></li> <li><strong>(release)</strong> handle draft visibility lag during staging by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/196">#196</a></li> <li><strong>(release)</strong> preserve the proposed tag when retargeting drafts by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/197">#197</a></li> </ul> <h3>📚 Documentation</h3> <ul> <li>clarify installation and the release specification by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/192">#192</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jdx/packslip/commit/7b32cd29a9240927882ee18b3db1dcfd8e0328b4"><code>7b32cd2</code></a> chore: release v1.7.0 (<a href="https://redirect.github.com/jdx/packslip/issues/228">#228</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/dbf98d50ca52ee75ad80dcee6be31bcf7073dc0d"><code>dbf98d5</code></a> chore: release v1.7.0 (<a href="https://redirect.github.com/jdx/packslip/issues/199">#199</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/002441fb5a7e984bcfa4ca71ff454362e5598a9b"><code>002441f</code></a> fix(verify): accept releases signed through another repository's reusable wor...</li> <li><a href="https://github.com/jdx/packslip/commit/7fb41123473054c2560f34763be6a44f4892e6d0"><code>7fb4112</code></a> chore(ci): switch to jactionlint v2 and drop zizmor (<a href="https://redirect.github.com/jdx/packslip/issues/225">#225</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/478b8c1237af72eb7ac1808d419e5652d504c6bb"><code>478b8c1</code></a> fix(deps): update rust crate usage-rs to v7 (<a href="https://redirect.github.com/jdx/packslip/issues/223">#223</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/468303e3968e5a0766df5c4aa39cb9859d2ea4af"><code>468303e</code></a> fix(deps): update rust crate usage_rs to v7 (<a href="https://redirect.github.com/jdx/packslip/issues/224">#224</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/a923451c938317da170158020b0e475cac768620"><code>a923451</code></a> ci: add shared release fix notifications (<a href="https://redirect.github.com/jdx/packslip/issues/222">#222</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/e89e4631e2d8d602759eb63f022183501f1028ab"><code>e89e463</code></a> chore(ci): lint workflows with jactionlint (<a href="https://redirect.github.com/jdx/packslip/issues/221">#221</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/597c0b5a96084d7a4034482d3787550fe1b92f8f"><code>597c0b5</code></a> chore: label release PRs with release (<a href="https://redirect.github.com/jdx/packslip/issues/220">#220</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/d34e18c466f332aeeec0f89fdcfa210698445161"><code>d34e18c</code></a> chore(deps): update rust crate lzma-rust2 to 0.21 (<a href="https://redirect.github.com/jdx/packslip/issues/219">#219</a>)</li> <li>Additional commits viewable in <a href="https://github.com/jdx/packslip/compare/2af36e792faa28130987c8af509e475c7458405d...7b32cd29a9240927882ee18b3db1dcfd8e0328b4">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
59fa0fed12 |
chore: bump taiki-e/install-action from 2.87.26 to 2.87.27 (#4445)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.26 to 2.87.27. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.27</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.32.0.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.24.</p> </li> <li> <p>Update <code>typos@latest</code> to 1.51.1.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.7.3.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.54.1.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.170.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.4.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.11.1.</p> </li> <li> <p>Update <code>hyperfine@latest</code> to 2.0.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.61.1.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.148.</p> </li> <li> <p>Update <code>cargo-neat@latest</code> to 0.6.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.2.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.27] - 2026-10-09</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.32.0.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.24.</p> </li> <li> <p>Update <code>typos@latest</code> to 1.51.1.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.7.3.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.54.1.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.170.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.4.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.11.1.</p> </li> <li> <p>Update <code>hyperfine@latest</code> to 2.0.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.61.1.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.148.</p> </li> <li> <p>Update <code>cargo-neat@latest</code> to 0.6.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.2.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/ab6895351a88b908e96a4697860d4ffea5e57dbe"><code>ab68953</code></a> Release 2.87.27</li> <li><a href="https://github.com/taiki-e/install-action/commit/62530fde5eae2d21742c80f8d06d4ddc2e1fc849"><code>62530fd</code></a> Update <code>vacuum@latest</code> to 0.32.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/f684ea4ef45b30adbd27018b3a8c8eff832d693e"><code>f684ea4</code></a> Update <code>uv@latest</code> to 0.12.24</li> <li><a href="https://github.com/taiki-e/install-action/commit/8aa87a079f6df0fefe32ea81cbf89957adfc4fb2"><code>8aa87a0</code></a> Update <code>typos@latest</code> to 1.51.1</li> <li><a href="https://github.com/taiki-e/install-action/commit/5ffcf4325f316f6461163dbceae21814184cc867"><code>5ffcf43</code></a> Update <code>tombi@latest</code> to 1.7.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/99266369a536fa5485f3e5b59913a332a0af45ff"><code>9926636</code></a> Update <code>syft@latest</code> to 1.54.1</li> <li><a href="https://github.com/taiki-e/install-action/commit/4647f42698f08ac3c2a60181bceea72db3556908"><code>4647f42</code></a> Update <code>release-plz@latest</code> to 0.3.170</li> <li><a href="https://github.com/taiki-e/install-action/commit/df0256079f1b5aae055d9e9826e16e43e37734d1"><code>df02560</code></a> Update rclone manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/d7c82f4c669484f523dfcd90e184702c32babdb1"><code>d7c82f4</code></a> Update <code>mise@latest</code> to 2026.10.4</li> <li><a href="https://github.com/taiki-e/install-action/commit/a6142d0c42332af2f8b733abb6a554272b9f5880"><code>a6142d0</code></a> Update <code>kingfisher@latest</code> to 2.11.1</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.26...v2.87.27">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
bf1d348c42 |
chore: update tend workflows (0.3.11 → 0.3.13) (#4438)
Regenerates the Tend workflows with tend 0.3.13 (from 0.3.11). The one behavior change in the generated files is that `tend-ci-fix` now starts only when a watched workflow on `main` **fails**; a cancelled run no longer starts a session, and the prompt drops its `Conclusion:` line since it is always a failure ([max-sixty/tend#1535](https://github.com/max-sixty/tend/pull/1535)). Every other workflow changes only its action pin. Other changes riding in with the new action version: - The bundled Claude Code CLI moves to 2.1.296 (max-sixty/tend#1536). - The CI skills weigh whether rerunning an unrelated CI failure is worth it before triggering the rerun (max-sixty/tend#1541). - A new opt-in `workflows.review.await_ci` setting lets a review finish without waiting for CI (max-sixty/tend#1538). This repo doesn't set it, so reviews behave as before. The PR also updates the nightly overlay (`.claude/skills/running-tend/references/nightly-cleaner.md`), which said `tend-ci-fix` fires on cancelled runs and reads a `Conclusion:` line. Neither holds after this upgrade. Full upstream diff: https://github.com/max-sixty/tend/compare/0.3.11...0.3.13 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
3e8278508d |
chore: bump astral-sh/setup-uv from 10.2.0 to 10.3.0 in /.github/actions/tend-setup (#4447)
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.2.0 to 10.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v10.3.0 🌈 Add Python architecture selection</h2> <h2>Changes</h2> <p>This release adds the <code>python-arch</code> input to select a Python architecture independently of the Python version. With <code>uv</code> 0.13.0 or later, set <code>python-arch: x86_64</code> to use x64 Python on Windows ARM64 runners.</p> <p>It also includes embedded checksums for <code>uv</code> releases through 0.13.0.</p> <ul> <li>Use macOS 15 runners for tests <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1081">#1081</a>)</li> </ul> <h2>🚀 Enhancements</h2> <ul> <li>Add <code>python-arch</code> support <a href="https://github.com/zanieb"><code>@zanieb</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1079">#1079</a>)</li> </ul> <h2>🧰 Maintenance</h2> <ul> <li>chore: update known checksums for 0.13.0 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1089">#1089</a>)</li> <li>chore: update known checksums for 0.12.24 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1084">#1084</a>)</li> <li>chore: update known checksums for 0.12.23 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1082">#1082</a>)</li> <li>chore: update known checksums for 0.12.22 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1080">#1080</a>)</li> <li>chore: update known checksums for 0.12.21 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1078">#1078</a>)</li> <li>chore: update known checksums for 0.12.20 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1076">#1076</a>)</li> <li>chore: update known checksums for 0.12.19 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1068">#1068</a>)</li> <li>chore: update known checksums for 0.12.18 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1065">#1065</a>)</li> </ul> <h2>⬆️ Dependency updates</h2> <ul> <li>chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1077">#1077</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/1c37ad07a6a961277cf70c0d37d6f313000f5884"><code>1c37ad0</code></a> chore: update known checksums for 0.13.0 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1089">#1089</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b3c9b5fc56ebc90760c43b1ac9552c0d1705d3ca"><code>b3c9b5f</code></a> chore: update known checksums for 0.12.24 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1084">#1084</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b06acff4b6a41bdd9cdac56507ead0bd7734e757"><code>b06acff</code></a> Add <code>python-arch</code> support (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1079">#1079</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c84232ca4fde9b022e20a930bfbbecd386b56fdf"><code>c84232c</code></a> chore: update known checksums for 0.12.23 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1082">#1082</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/51fdd265d38a27ffcbca0da885510bc6fcc0ff55"><code>51fdd26</code></a> Use macOS 15 runners for tests (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1081">#1081</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a96208bed1fb5efb8da349c9bcc6cc58af9e7d74"><code>a96208b</code></a> chore: update known checksums for 0.12.22 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1080">#1080</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/0e3884b860e20d3f4d5daa2347130beb51ccde47"><code>0e3884b</code></a> chore: update known checksums for 0.12.21 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1078">#1078</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/bcf05803b55ef01a5ec6368521ee1b42f97bc438"><code>bcf0580</code></a> chore: update known checksums for 0.12.20 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1076">#1076</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b92a892142bde7280cd163c2abff341413314f9f"><code>b92a892</code></a> chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1077">#1077</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/227a0f6bea25cde3444f52decccf4a18de6635f4"><code>227a0f6</code></a> chore: update known checksums for 0.12.19 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1068">#1068</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/setup-uv/compare/v10.2.0...v10.3.0">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
67cc6d9d8a |
chore: bump astral-sh/setup-uv from 10.2.0 to 10.3.0 (#4446)
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.2.0 to 10.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v10.3.0 🌈 Add Python architecture selection</h2> <h2>Changes</h2> <p>This release adds the <code>python-arch</code> input to select a Python architecture independently of the Python version. With <code>uv</code> 0.13.0 or later, set <code>python-arch: x86_64</code> to use x64 Python on Windows ARM64 runners.</p> <p>It also includes embedded checksums for <code>uv</code> releases through 0.13.0.</p> <ul> <li>Use macOS 15 runners for tests <a href="https://github.com/charliermarsh"><code>@charliermarsh</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1081">#1081</a>)</li> </ul> <h2>🚀 Enhancements</h2> <ul> <li>Add <code>python-arch</code> support <a href="https://github.com/zanieb"><code>@zanieb</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1079">#1079</a>)</li> </ul> <h2>🧰 Maintenance</h2> <ul> <li>chore: update known checksums for 0.13.0 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1089">#1089</a>)</li> <li>chore: update known checksums for 0.12.24 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1084">#1084</a>)</li> <li>chore: update known checksums for 0.12.23 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1082">#1082</a>)</li> <li>chore: update known checksums for 0.12.22 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1080">#1080</a>)</li> <li>chore: update known checksums for 0.12.21 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1078">#1078</a>)</li> <li>chore: update known checksums for 0.12.20 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1076">#1076</a>)</li> <li>chore: update known checksums for 0.12.19 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1068">#1068</a>)</li> <li>chore: update known checksums for 0.12.18 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1065">#1065</a>)</li> </ul> <h2>⬆️ Dependency updates</h2> <ul> <li>chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 @<a href="https://github.com/apps/dependabot">dependabot[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1077">#1077</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/1c37ad07a6a961277cf70c0d37d6f313000f5884"><code>1c37ad0</code></a> chore: update known checksums for 0.13.0 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1089">#1089</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b3c9b5fc56ebc90760c43b1ac9552c0d1705d3ca"><code>b3c9b5f</code></a> chore: update known checksums for 0.12.24 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1084">#1084</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b06acff4b6a41bdd9cdac56507ead0bd7734e757"><code>b06acff</code></a> Add <code>python-arch</code> support (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1079">#1079</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c84232ca4fde9b022e20a930bfbbecd386b56fdf"><code>c84232c</code></a> chore: update known checksums for 0.12.23 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1082">#1082</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/51fdd265d38a27ffcbca0da885510bc6fcc0ff55"><code>51fdd26</code></a> Use macOS 15 runners for tests (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1081">#1081</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a96208bed1fb5efb8da349c9bcc6cc58af9e7d74"><code>a96208b</code></a> chore: update known checksums for 0.12.22 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1080">#1080</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/0e3884b860e20d3f4d5daa2347130beb51ccde47"><code>0e3884b</code></a> chore: update known checksums for 0.12.21 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1078">#1078</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/bcf05803b55ef01a5ec6368521ee1b42f97bc438"><code>bcf0580</code></a> chore: update known checksums for 0.12.20 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1076">#1076</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b92a892142bde7280cd163c2abff341413314f9f"><code>b92a892</code></a> chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1077">#1077</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/227a0f6bea25cde3444f52decccf4a18de6635f4"><code>227a0f6</code></a> chore: update known checksums for 0.12.19 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1068">#1068</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/setup-uv/compare/c18668ad3cf93ea998bef934396af7bb5c839dc7...1c37ad07a6a961277cf70c0d37d6f313000f5884">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
8e3bd31a27 |
ci: bump Nushell pin to 0.116.1 (#4431)
This moves the pinned Nushell from 0.116.0 to [0.116.1](https://github.com/nushell/nushell/releases/tag/0.116.1) at every call site: the `hustcer/setup-nu` inputs in `coverage.yaml`, `nightly.yaml`, `benchmarks.yaml`, and the `test-setup` and `tend-setup` actions; `.codex/cloud.sh`; and the `setup-web` task in `Taskfile.yaml`. Nushell is the third tool the Codex Cloud script keeps level with `test-setup`, which is why those two move together. This PR is separate from the weekly `cargo-nextest` bump (#4430) because a Nushell version can change PTY snapshots under `--all-features`. That keeps any snapshot fallout here. The `code-coverage` and test jobs on this PR exercise the new version. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
7f588e01ae |
ci: bump cargo-nextest pin to 0.9.148 (#4430)
This moves the pinned `cargo-nextest` from 0.9.146 to 0.9.148 everywhere it's pinned: `coverage.yaml`, the `test-setup` and `tend-setup` actions, and `.codex/cloud.sh`. All four stay level, as the Codex Cloud script requires. 0.9.148 needs Rust 1.91, and our toolchain is 1.98.0. The one behavior change in [0.9.148](https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.148) is that setup scripts no longer accept `slow-timeout.on-timeout = "pass"`. `.config/nextest.toml` doesn't set it. Everything else in the release is a fix: stress-run exit codes, leak-timeout handling, and how timeout and cancellation are reported. The other weekly pin checks found no drift apart from Nushell 0.116.1, which has its own PR because a Nushell version can move PTY snapshots. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
adcb3fd3f2 |
chore: update tend workflows (0.3.10 → 0.3.11) (#4423)
Regenerates the Tend workflows for tend 0.3.10 → 0.3.11. The only change in the generated files is the action pin (`max-sixty/tend/claude@0.3.11`) and the version header; no triggers, permissions, or setup steps change. What the new version changes for this repo is small, because worktrunk runs in `restricted` merge mode: - `tend init` now stops before writing workflows when it can't read the canonical repository owner, instead of continuing past the fork guard (max-sixty/tend#1522). - The `yolo` merge path now follows the repository's CI policy and treats GitHub's merge API response as the verdict (max-sixty/tend#1528). This repo uses `restricted`, so the bot still never merges here; the related wording updates in the bundled skills and system prompt don't change what it does on worktrunk. Full diff: https://github.com/max-sixty/tend/compare/0.3.10...0.3.11 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
4702e1481a |
Gate signing and host OIDC through the release environment (#4415)
The release workflow's `host` job granted OIDC token access without an environment gate. It now uses the tag-only `release` environment, and Windows signing shares that environment because `signing` had the same admin-controlled tag policy. The SignPath CI token has been rotated and provisioned in both environments before this change. Credentials remain explicit inputs to their consuming steps; the shared environment makes all release secrets available through the jobs' secrets context. This also gives `host` the documented `release` scope used by crates.io Trusted Publishing. Validated with the project pre-merge checks, actionlint, an independent security-boundary review, and Tend's credential-environment check against live GitHub policies: the original workflow fails on `host`, and this workflow passes. Fixes #4312. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
6209c17d99 |
chore: bump taiki-e/install-action from 2.87.24 to 2.87.26 (#4403)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.24 to 2.87.26. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.26</h2> <ul> <li> <p>Update <code>tombi@latest</code> to 1.7.2.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.5.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.3.</p> </li> <li> <p>Update <code>kache@latest</code> to 1.0.0.</p> </li> <li> <p>Update <code>hyperfine@latest</code> to 1.21.0.</p> </li> </ul> <h2>2.87.25</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.23.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.2.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.10.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.60.1.</p> </li> <li> <p>Update <code>cargo-semver-checks@latest</code> to 0.51.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.1.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.26] - 2026-10-06</h2> <ul> <li> <p>Update <code>tombi@latest</code> to 1.7.2.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.5.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.3.</p> </li> <li> <p>Update <code>kache@latest</code> to 1.0.0.</p> </li> <li> <p>Update <code>hyperfine@latest</code> to 1.21.0.</p> </li> </ul> <h2>[2.87.25] - 2026-10-05</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.23.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.2.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.10.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.60.1.</p> </li> <li> <p>Update <code>cargo-semver-checks@latest</code> to 0.51.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.1.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/f7e5d7c961414b23f5b25b2da9294395d08513ad"><code>f7e5d7c</code></a> Release 2.87.26</li> <li><a href="https://github.com/taiki-e/install-action/commit/148b70c8533f32f0f67928d48f6234c224cc2717"><code>148b70c</code></a> Update <code>tombi@latest</code> to 1.7.2</li> <li><a href="https://github.com/taiki-e/install-action/commit/9856be60d227976dcbe71f75a36a857c6bf3504a"><code>9856be6</code></a> Update <code>prek@latest</code> to 0.5.5</li> <li><a href="https://github.com/taiki-e/install-action/commit/246da9e6f2857c0c408cc9b590117673cd74d06e"><code>246da9e</code></a> Update <code>mise@latest</code> to 2026.10.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/8ec05a70c3252cd782c8c266ee7c57fdfa6b0699"><code>8ec05a7</code></a> Update <code>kache@latest</code> to 1.0.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/a5ed626e494481910920bbdee016db18f33bf1df"><code>a5ed626</code></a> Update <code>hyperfine@latest</code> to 1.21.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/183e4297cca2404691e9380e1307288dced5c82a"><code>183e429</code></a> Release 2.87.25</li> <li><a href="https://github.com/taiki-e/install-action/commit/5e241e4899f64a7ba9011f0c3a46f591b6527640"><code>5e241e4</code></a> Update <code>uv@latest</code> to 0.12.23</li> <li><a href="https://github.com/taiki-e/install-action/commit/126791b91b3ba2303cb850bbdb6943156fe7c71b"><code>126791b</code></a> Update tombi manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/35ba21c90f3f48ed80e4934a494a422e17488157"><code>35ba21c</code></a> Update prek manifest</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.24...v2.87.26">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
4f4611e8f5 |
chore: bump taiki-e/install-action from 2.87.23 to 2.87.24 (#4387)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.23 to 2.87.24. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.24</h2> <ul> <li> <p>Update <code>wasmtime@latest</code> to 49.0.2.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.59.0.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.11.</p> </li> <li> <p>Update <code>cargo-insta@latest</code> to 1.49.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.24] - 2026-10-04</h2> <ul> <li> <p>Update <code>wasmtime@latest</code> to 49.0.2.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.59.0.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.11.</p> </li> <li> <p>Update <code>cargo-insta@latest</code> to 1.49.0.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.25.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/e407f7bafb71fd004bc5c2da3032e5470cbb6ef0"><code>e407f7b</code></a> Release 2.87.24</li> <li><a href="https://github.com/taiki-e/install-action/commit/cf05ef864e9f66eb375f5000cc71cb3f90bede2b"><code>cf05ef8</code></a> Update wasmtime manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/a9843d29aa80dad318a30939972ff077b7c0c1ed"><code>a9843d2</code></a> Update <code>wasmtime@latest</code> to 49.0.2</li> <li><a href="https://github.com/taiki-e/install-action/commit/b53f18d3272788dee0a574080a98fc2dbe92f0aa"><code>b53f18d</code></a> Update uv manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/432553710dc21b4f7270c670f4620f829d5c9375"><code>4325537</code></a> Update kingfisher manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/28c75969bb18dc23fe25a37a2f47b5fd2af27dd1"><code>28c7596</code></a> Update <code>dprint@latest</code> to 0.59.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/c9ccaaeffe99c9f74245f88f8e736dc8b8524c8f"><code>c9ccaae</code></a> Update cargo-semver-checks manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/6a93a472a4fadcaa3c041e569eee39d762923f84"><code>6a93a47</code></a> Update <code>cargo-leptos@latest</code> to 0.3.11</li> <li><a href="https://github.com/taiki-e/install-action/commit/32465026f914ad462743179999c65b9773d2d9ff"><code>3246502</code></a> Update <code>cargo-insta@latest</code> to 1.49.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/944f981294fb92b4c2bb873d2fa0b5fd61f613bb"><code>944f981</code></a> Update <code>cargo-binstall@latest</code> to 1.25.0</li> <li>See full diff in <a href="https://github.com/taiki-e/install-action/compare/v2.87.23...v2.87.24">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
e71d4d87bd |
chore: bump jdx/packslip from 1.5.1 to 1.6.0 (#4388)
Bumps [jdx/packslip](https://github.com/jdx/packslip) from 1.5.1 to 1.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/releases">jdx/packslip's releases</a>.</em></p> <blockquote> <h2>v1.6.0: The GitHub Action checks the packslip CLI it downloads against a SHA-256 pinned in the action commit</h2> <p>The <code>jdx/packslip</code> GitHub Action now checks the packslip CLI archive it downloads against a SHA-256 digest stored in the action commit itself. Pinning the action to a full commit SHA therefore also pins the CLI it runs. Release builds now come from a reviewed candidate, which changes the provenance of packslip's own release files (see Changed). The packslip format is unchanged and still version 1.</p> <h2>Added</h2> <ul> <li><strong>The action checks the default CLI download against a pinned digest.</strong> Each released action commit now includes <code>action/release.json</code>, which holds the SHA-256 of the CLI archive for all five supported platforms. With the default CLI version, the action checks the downloaded archive against that digest before it verifies provenance or extracts anything. It stops with an error if the digest is missing, malformed, or doesn't match. Provenance is then checked against the exact commit and workflow that built the archive. Your workflow doesn't need its own per-platform hashes. (<a href="https://redirect.github.com/jdx/packslip/issues/194">#194</a>, <a href="https://redirect.github.com/jdx/packslip/issues/195">#195</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <pre lang="yaml"><code>- uses: jdx/packslip@<full-commit-sha> # v1.6.0 </code></pre> </li> <li><strong>New <code>packslip-sha256</code> input</strong> for the action and for <code>jdx/packslip/releases</code>. It pins the downloaded archive when you set <code>packslip-version</code> explicitly. With the default version, a digest you supply must match the action's own copy. The input is ignored when <code>packslip-path</code> is set. (<a href="https://redirect.github.com/jdx/packslip/issues/194">#194</a>, <a href="https://redirect.github.com/jdx/packslip/issues/195">#195</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <pre lang="yaml"><code>- uses: jdx/packslip@<full-commit-sha> with: packslip-version: 1.5.1 packslip-sha256: d401822be0f4c0494dde170657499fc197709b530e18b547906dafe05c155d45 </code></pre> An explicit <code>packslip-version</code> without <code>packslip-sha256</code> keeps the old provenance-only check and prints a warning.</li> </ul> <h2>Changed</h2> <ul> <li><strong>New release process and provenance for packslip's own releases.</strong> Starting with this release, packslip's binaries are built, signed, and attested from the release PR's <code>release-plz</code> branch before any version tag exists. The tag then publishes those same files without rebuilding them. Their build provenance therefore names the candidate commit on <code>refs/heads/release-plz</code>, not <code>refs/tags/vX.Y.Z</code>. The signed packslip.dev manifest records that build commit and leaves out <code>source.tag</code>. If you verify packslip downloads with a policy that requires a build from the tag, such as <code>gh attestation verify --source-ref refs/tags/v1.6.0</code>, that check will fail; update the policy. The action's <code>vX.Y.Z</code> tag and the CLI release tag point to the same commit, and <code>v1</code> moves to it after publication. (<a href="https://redirect.github.com/jdx/packslip/issues/195">#195</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> </ul> <h2>Breaking Changes</h2> <p>These apply only to the GitHub Action, not to the CLI or the format.</p> <ul> <li><strong>Runners need <code>jq</code></strong> to read the action's digest file. GitHub-hosted runners already include it. On self-hosted runners and some macOS runners, install it before the action runs.</li> <li><strong>Pin the action to a released commit, or set <code>packslip-version</code>.</strong> With the default CLI version, a checkout that has no <code>action/release.json</code> now fails with "the action checkout has no release digest map". This includes <code>@main</code> and any unreleased commit. Use a release tag or a release commit SHA. You can also set <code>packslip-version</code>, optionally with <code>packslip-sha256</code>, or set <code>packslip-path</code>.</li> </ul> <h2>Documentation</h2> <ul> <li>The documentation is now organized around tasks. It covers installing the packslip CLI, installing tools such as mise with <code>packslip install --pin</code>, using packslip with mise in both directions, installing packslip from the signed APT/RPM repositories, and pinning the container image by digest. The site header's "Spec & schemas" link now goes to <code>/release/v1/</code>, which links to downloadable schemas and explains what schema validation does and doesn't check. (<a href="https://redirect.github.com/jdx/packslip/issues/192">#192</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jdx/packslip/compare/v1.5.1...v1.6.0">https://github.com/jdx/packslip/compare/v1.5.1...v1.6.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/blob/main/CHANGELOG.md">jdx/packslip's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2><a href="https://github.com/jdx/packslip/compare/v1.5.1..v1.6.0">1.6.0</a> - 2026-10-05</h2> <h3>🚀 Features</h3> <ul> <li><strong>(action)</strong> lock released CLI archive digests by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/194">#194</a></li> </ul> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(action)</strong> pin candidate archives before the shared release tag by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/195">#195</a></li> <li><strong>(release)</strong> handle draft visibility lag during staging by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/196">#196</a></li> <li><strong>(release)</strong> preserve the proposed tag when retargeting drafts by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/197">#197</a></li> </ul> <h3>📚 Documentation</h3> <ul> <li>clarify installation and the release specification by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/192">#192</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.5.0..v1.5.1">1.5.1</a> - 2026-10-04</h2> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(install)</strong> install under a group-writable umask such as Debian's 002 by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/188">#188</a></li> <li><strong>(install)</strong> create a missing extraction parent without group write by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/189">#189</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.4.0..v1.5.0">1.5.0</a> - 2026-10-04</h2> <h3>🚀 Features</h3> <ul> <li><strong>(cli)</strong> add a verifier-only build for distro packaging by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/165">#165</a></li> <li><strong>(discovery)</strong> resolve bootstrap releases with bounded HTTPS downloads by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/167">#167</a></li> <li><strong>(forge)</strong> let consumers compare signers, hold several pins, and keep accepted owners across transfers by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/136">#136</a></li> <li><strong>(forge)</strong> pin a keyless signer with a short ps1_ fingerprint by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/154">#154</a></li> <li><strong>(install)</strong> stage complete artifacts with bounded safe extraction by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/170">#170</a></li> <li><strong>(install)</strong> recover transactional tree and command replacement by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/175">#175</a></li> <li><strong>(install)</strong> export native Windows command launchers by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/176">#176</a></li> <li><strong>(install)</strong> check selected artifact host requirements by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/177">#177</a></li> <li><strong>(install)</strong> bootstrap authenticated releases in user and system scopes by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/184">#184</a></li> <li><strong>(packaging)</strong> build the installer offline with distro Rust toolchains by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/186">#186</a></li> <li><strong>(packaging)</strong> distribute native installers through signed APT and RPM repositories by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/187">#187</a></li> <li><strong>(spec)</strong> let reusable-workflow vendors opt out of workflow pinning by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/153">#153</a></li> <li><strong>(trust)</strong> refresh Sigstore keys through authenticated TUF history by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/166">#166</a></li> <li><strong>(trust)</strong> enforce bootstrap pins and remembered signer continuity by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/169">#169</a></li> <li>publish a packslip agent skill with releases by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/139">#139</a></li> <li>install packslip from packslip.sh with checksum-pinned scripts by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/174">#174</a></li> <li>publish packslip as a multi-arch container image on ghcr.io by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/179">#179</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jdx/packslip/commit/2af36e792faa28130987c8af509e475c7458405d"><code>2af36e7</code></a> chore: release v1.6.0 (<a href="https://redirect.github.com/jdx/packslip/issues/193">#193</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/54f29eb6bd6c56d5b6531db4c64b555f96344f11"><code>54f29eb</code></a> fix(release): preserve the proposed tag when retargeting drafts (<a href="https://redirect.github.com/jdx/packslip/issues/197">#197</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/36da313c9ba503bd1d1762aaf0c27ef750ad6049"><code>36da313</code></a> fix(release): handle draft visibility lag during staging (<a href="https://redirect.github.com/jdx/packslip/issues/196">#196</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/3fe7a61963712b67c933c5b1fe4f8985e96fba8f"><code>3fe7a61</code></a> fix(action): pin candidate archives before the shared release tag (<a href="https://redirect.github.com/jdx/packslip/issues/195">#195</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/972c1e1ccc51cb512ef2cf17e7a3708106c692f9"><code>972c1e1</code></a> feat(action): lock released CLI archive digests (<a href="https://redirect.github.com/jdx/packslip/issues/194">#194</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/b3134ffc4a55a090ce18ffd11cc4fe54470d30b1"><code>b3134ff</code></a> docs: clarify installation and the release specification (<a href="https://redirect.github.com/jdx/packslip/issues/192">#192</a>)</li> <li>See full diff in <a href="https://github.com/jdx/packslip/compare/22be7aeb840156291e1ae795ca37b36a2dc1969c...2af36e792faa28130987c8af509e475c7458405d">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
c622789963 |
chore: update tend workflows (0.3.9 → 0.3.10) (#4390)
Updates the generated Tend workflows from 0.3.9 to 0.3.10. The workflow diff is only the version stamp and the `max-sixty/tend/claude@0.3.10` action pin; the behavior change comes with the action and bundled skills. What changes for this repo: - **Flaky PR tests get an owner instead of just a rerun.** When a review finds a check failing for reasons unrelated to the PR, it now waits for the rerun's result and routes the failure: infrastructure blips are named in the summary, failures `main` also shows are left to `ci-fix`, and a project test that fails on the PR while `main` passes it gets an issue (or an appended run on the existing one), which `tend-triage` then picks up (max-sixty/tend#1518). Expect occasional new bot-filed issues naming an intermittently failing test. - **The action's runtime ships as the `tend` package** and runs through `tend runtime …` commands rather than loose scripts (max-sixty/tend#1512). No consumer configuration changes; it should be invisible apart from setup logs. No model defaults changed for the Claude harness, and `.config/tend.yaml` carries no model pins, so nothing there was edited. Full upstream diff: https://github.com/max-sixty/tend/compare/0.3.9...0.3.10 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
5ba80ce6c0 |
chore: bump taiki-e/install-action from 2.87.22 to 2.87.23 (#4380)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.22 to 2.87.23. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.23</h2> <ul> <li> <p>Update <code>wasm-tools@latest</code> to 1.261.0.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.22.</p> </li> <li> <p>Update <code>trivy@latest</code> to 0.75.0.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.7.1.</p> </li> <li> <p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.28.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.0.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.9.1.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.28.1.</p> </li> <li> <p>Update <code>espup@latest</code> to 0.18.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.58.0.</p> </li> <li> <p>Update <code>cargo-crap@latest</code> to 0.6.1.</p> </li> <li> <p>Update <code>cargo-auditable@latest</code> to 0.7.7.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.5.15.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.54.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.23] - 2026-10-03</h2> <ul> <li> <p>Update <code>wasm-tools@latest</code> to 1.261.0.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.22.</p> </li> <li> <p>Update <code>trivy@latest</code> to 0.75.0.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.7.1.</p> </li> <li> <p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.28.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.0.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.9.1.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.28.1.</p> </li> <li> <p>Update <code>espup@latest</code> to 0.18.0.</p> </li> <li> <p>Update <code>dprint@latest</code> to 0.58.0.</p> </li> <li> <p>Update <code>cargo-crap@latest</code> to 0.6.1.</p> </li> <li> <p>Update <code>cargo-auditable@latest</code> to 0.7.7.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.5.15.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.54.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/861a07ce7084f55488e375df125cdc99bba60eb7"><code>861a07c</code></a> Release 2.87.23</li> <li><a href="https://github.com/taiki-e/install-action/commit/92495f8737e120f7744bf20e301598a2e40deda5"><code>92495f8</code></a> Bump taiki-e/github-actions/.github/workflows/tidy.yml</li> <li><a href="https://github.com/taiki-e/install-action/commit/bfc83a3f88b452907272ddd6be669234117f3d7a"><code>bfc83a3</code></a> Bump taiki-e/github-actions/.github/workflows/rust-test.yml</li> <li><a href="https://github.com/taiki-e/install-action/commit/d83652f51440bc953f2bbba2e2456156e3fcbe26"><code>d83652f</code></a> Bump taiki-e/github-actions/.github/workflows/rust-release.yml</li> <li><a href="https://github.com/taiki-e/install-action/commit/8f5ec36575116f05162369f337f2c2a942e5d56f"><code>8f5ec36</code></a> Bump taiki-e/github-actions/.github/workflows/action-release.yml</li> <li><a href="https://github.com/taiki-e/install-action/commit/735d46fcdbb05b57a3b62365608c5363ca1189bb"><code>735d46f</code></a> Bump taiki-e/github-actions/.github/workflows/gen.yml</li> <li><a href="https://github.com/taiki-e/install-action/commit/ec4a33f6acd691bf1474b5bb13ac342473aec595"><code>ec4a33f</code></a> Update wasmtime manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/b3891286622d5cc1ba5d4e1b64dffe34832a8f58"><code>b389128</code></a> Update <code>wasm-tools@latest</code> to 1.261.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/d4f74b0633bf86f33aa3ef85105fd69564834b26"><code>d4f74b0</code></a> Update <code>uv@latest</code> to 0.12.22</li> <li><a href="https://github.com/taiki-e/install-action/commit/f97a9bc741176719488ef66ff2a6512a990bf15c"><code>f97a9bc</code></a> Update <code>trivy@latest</code> to 0.75.0</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.22...v2.87.23">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
e2f0126194 |
chore: bump jdx/packslip from 1.4.0 to 1.5.1 (#4381)
Bumps [jdx/packslip](https://github.com/jdx/packslip) from 1.4.0 to 1.5.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/releases">jdx/packslip's releases</a>.</em></p> <blockquote> <h2>v1.5.1: Fix <code>packslip install</code> under a group-writable umask such as Debian's 002</h2> <p><code>packslip install</code> now works for ordinary users on Debian, Ubuntu, and other systems whose login umask is <code>002</code>. In 1.5.0 it failed for these users. The packslip format is unchanged and still version 1.</p> <h2>Fixed</h2> <ul> <li><strong><code>packslip install</code> no longer refuses its own directories under umask <code>002</code>.</strong> With a user-private-group umask, the directories the installer created were group-writable (<code>0775</code>), and its safety check then rejected them (<a href="https://redirect.github.com/jdx/packslip/issues/188">#188</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>): <pre lang="console"><code>$ packslip install github.com/jdx/mise Error: 0: /home/u/.local/share/packslip/.packslip-stage-X0jH5v has unsafe directory ownership or permissions </code></pre> The installer now sets directory modes explicitly instead of relying on the umask. Staging, transaction, command-export, and state directories are <code>0700</code>. The extracted tree and the download cache are <code>0755</code>. The safety check has not changed and still refuses any directory another user can write to. Root installs and CI usually run with umask <code>022</code>, so they were not affected.</li> <li><strong>Library:</strong> <code>install_extract::extract</code> now creates a missing <code>parent</code> directory as <code>0755</code>, matching the rest of the extracted tree. Before, it used the process umask and could leave the directory group-writable. <code>packslip install</code> itself was not affected because it always passes a parent that already exists. (<a href="https://redirect.github.com/jdx/packslip/issues/189">#189</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> </ul> <h2>Documentation</h2> <ul> <li>The getting-started guide now shows the two install methods added in 1.5.0. For the packslip.sh script, it covers <code>curl -fsSL https://packslip.sh | sh</code>, the PowerShell equivalent, <code>PACKSLIP_BIN_DIR</code>, per-release checksum-pinned URLs, and <code>gh attestation verify</code>. For the <code>ghcr.io/jdx/packslip</code> container image, it shows how to pin it by digest. (<a href="https://redirect.github.com/jdx/packslip/issues/181">#181</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>)</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jdx/packslip/compare/v1.5.0...v1.5.1">https://github.com/jdx/packslip/compare/v1.5.0...v1.5.1</a></p> <h2>v1.5.0: packslip install, signer fingerprints, and new ways to install packslip</h2> <p><code>packslip install</code> adds a new way to consume releases: it verifies a publisher's signed release, then installs the whole artifact tree and exports only the commands the release declares. This release also adds short <code>ps1_</code> signer fingerprints for pinning, treats repository transfers like renames, and adds new ways to get packslip itself: packslip.sh, a container image, and distribution packaging. The packslip format is still version 1. Its only format change is the optional <code>identity.pin_workflow</code> field, which version 1 allows. A few library and <code>--json</code> changes may need attention (see Breaking Changes).</p> <h2>Highlights</h2> <ul> <li><strong>Verified installs.</strong> <code>packslip install</code> puts together several new library layers: release discovery, Sigstore TUF refresh, pins with signer-continuity checks, safe archive extraction, host-requirement checks, recoverable replacement, and native command launchers on Windows.</li> <li><strong>Stable identity across renames and transfers.</strong> A <code>ps1_</code> fingerprint names a repository by forge issuer and repository ID. The fingerprint stays the same through renames, transfers, and workflow changes. Vendors that sign from reusable workflows can now opt out of workflow pinning.</li> <li><strong>New ways to get packslip.</strong> packslip.sh install scripts, <code>ghcr.io/jdx/packslip</code>, standalone executables in each release, Windows builds that need no Visual C++ runtime, and offline recipes for distribution packages.</li> </ul> <h2>Added</h2> <h3><code>packslip install</code></h3> <ul> <li><strong><code>packslip install</code> installs a signed upstream release</strong> without running any downloaded code or editing shell config. It discovers the release from GitHub, or from a host's signed well-known list, and verifies the release and its release list. It then checks host requirements, extracts the complete tree (bundled runtimes stay off PATH), and exports the declared commands. On Unix these are symlinks. On Windows they are small native <code>.exe</code> launchers that don't need Developer Mode. (<a href="https://redirect.github.com/jdx/packslip/issues/184">#184</a>, <a href="https://redirect.github.com/jdx/packslip/issues/170">#170</a>, <a href="https://redirect.github.com/jdx/packslip/issues/175">#175</a>, <a href="https://redirect.github.com/jdx/packslip/issues/176">#176</a>, <a href="https://redirect.github.com/jdx/packslip/issues/177">#177</a>, <a href="https://redirect.github.com/jdx/packslip/issues/167">#167</a>, <a href="https://redirect.github.com/jdx/packslip/issues/171">#171</a>, <a href="https://redirect.github.com/jdx/packslip/issues/169">#169</a>, <a href="https://redirect.github.com/jdx/packslip/issues/166">#166</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <pre lang="sh"><code>packslip install github.com/jdx/mise packslip install owner/repo --version 1.2 packslip install tool.example.com --pubkey /path/to/vendor.pub sudo packslip install owner/repo --system </code></pre> <ul> <li><strong>Scopes:</strong> user scope (XDG paths on Unix, LocalAppData on Windows) or <code>--system</code> scope (<code>/opt/packslip</code> and <code>/usr/local/bin</code>, or Program Files). Root uses system scope by default and ignores user configuration. <code>--install-dir</code> and <code>--bin-dir</code> change where files go but not where trust state is kept.</li> <li><strong>Trust:</strong> <code>--pin</code>, <code>--pubkey</code>, <code>--identity</code>, <code>--identity-prefix</code>, and <code>--issuer</code> set requirements for this call. Administrator TOML files in <code>/etc/packslip/pins.d/</code>, plus a user-level equivalent, add requirements of their own, and every requirement must pass. Releases and release lists keep separate records of the signer they last accepted. A change in signer, workflow, repository ID, signing scheme, or provenance is refused until approved with the exact <code>--accept-trust-change=<id></code> that the refusal prints.</li> <li><strong>Safety:</strong> list sequence history is saved before anything is downloaded, so a failed attempt can't make an older list acceptable again. Expired, withdrawn, or rolled-back metadata is refused, even with <code>--force</code>. Replacements are journaled and recovered after an interruption. <code>--force</code> only allows replacing conflicting commands and unmarked directories. Extraction rejects path escapes and special entries, and defaults to limits of 10 GiB and 100,000 entries (<code>--max-extracted-size</code>, <code>--max-archive-entries</code>). An incompatible OS, glibc, or library requirement blocks the install unless you pass <code>--allow-incompatible-host</code>.</li> <li><strong>Offline and credentials:</strong> <code>--offline</code> uses only cached authenticated metadata and artifacts. <code>GH_TOKEN</code>/<code>GITHUB_TOKEN</code> apply to GitHub. Other bearer tokens are scoped to an exact HTTPS origin in <code>config.toml</code>.</li> <li><strong>Limits:</strong> forge discovery supports GitHub only for now. Supported targets are Linux x64/ARM64, macOS ARM64, and Windows x64/ARM64. Resources are recorded as metadata but are not executed or exported. Real-world setup with mise, rustup, uv, and pnpm has not been verified yet. The new <a href="https://packslip.dev/docs/compatibility/">compatibility and support matrix</a> lists what CI covers and which checks are still outstanding (<a href="https://redirect.github.com/jdx/packslip/issues/185">#185</a>).</li> </ul> </li> <li><strong>Library:</strong> each install layer is behind its own optional Cargo feature: <code>trust-root</code>, <code>discovery</code>, <code>install-policy</code>, <code>install-extract</code>, <code>install-fs</code>, <code>install-launcher</code>, and <code>install-host</code>. <code>trust-root</code> refreshes Sigstore verification material from a pinned TUF root, including after that root has expired. It replays a cached refresh offline and refuses rollback and corruption.</li> </ul> <h3>Signer fingerprints and forge identity</h3> <ul> <li><strong><code>packslip pin</code> and <code>packslip verify --pin</code>.</strong> A vendor can publish a short fingerprint such as <code>ps1_snirenkjwr7m5ozgcufameodnm</code> in its README. Consumers then don't have to trust whatever a project name resolves to the first time they use it. The fingerprint is built only from the forge issuer and the repository ID. It stays the same through a rename, a transfer, or a new workflow, and a repository recreated under an old name gets a different one. Key-signed releases and certificates without a repository ID have no fingerprint. The library exposes this as <code>packslip::fingerprint::Fingerprint</code>, and conformance vectors are in <code>tests/conformance/signer-fingerprint.json</code>. (<a href="https://redirect.github.com/jdx/packslip/issues/154">#154</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>) <pre lang="sh"><code>$ packslip pin packslip.sigstore.json ps1_snirenkjwr7m5ozgcufameodnm $ packslip verify packslip.sigstore.json --pin ps1_snirenkjwr7m5ozgcufameodnm </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/blob/main/CHANGELOG.md">jdx/packslip's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2><a href="https://github.com/jdx/packslip/compare/v1.5.1..v1.6.0">1.6.0</a> - 2026-10-05</h2> <h3>🚀 Features</h3> <ul> <li><strong>(action)</strong> lock released CLI archive digests by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/194">#194</a></li> </ul> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(action)</strong> pin candidate archives before the shared release tag by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/195">#195</a></li> <li><strong>(release)</strong> handle draft visibility lag during staging by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/196">#196</a></li> <li><strong>(release)</strong> preserve the proposed tag when retargeting drafts by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/197">#197</a></li> </ul> <h3>📚 Documentation</h3> <ul> <li>clarify installation and the release specification by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/192">#192</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.5.0..v1.5.1">1.5.1</a> - 2026-10-04</h2> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(install)</strong> install under a group-writable umask such as Debian's 002 by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/188">#188</a></li> <li><strong>(install)</strong> create a missing extraction parent without group write by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/189">#189</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.4.0..v1.5.0">1.5.0</a> - 2026-10-04</h2> <h3>🚀 Features</h3> <ul> <li><strong>(cli)</strong> add a verifier-only build for distro packaging by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/165">#165</a></li> <li><strong>(discovery)</strong> resolve bootstrap releases with bounded HTTPS downloads by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/167">#167</a></li> <li><strong>(forge)</strong> let consumers compare signers, hold several pins, and keep accepted owners across transfers by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/136">#136</a></li> <li><strong>(forge)</strong> pin a keyless signer with a short ps1_ fingerprint by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/154">#154</a></li> <li><strong>(install)</strong> stage complete artifacts with bounded safe extraction by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/170">#170</a></li> <li><strong>(install)</strong> recover transactional tree and command replacement by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/175">#175</a></li> <li><strong>(install)</strong> export native Windows command launchers by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/176">#176</a></li> <li><strong>(install)</strong> check selected artifact host requirements by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/177">#177</a></li> <li><strong>(install)</strong> bootstrap authenticated releases in user and system scopes by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/184">#184</a></li> <li><strong>(packaging)</strong> build the installer offline with distro Rust toolchains by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/186">#186</a></li> <li><strong>(packaging)</strong> distribute native installers through signed APT and RPM repositories by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/187">#187</a></li> <li><strong>(spec)</strong> let reusable-workflow vendors opt out of workflow pinning by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/153">#153</a></li> <li><strong>(trust)</strong> refresh Sigstore keys through authenticated TUF history by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/166">#166</a></li> <li><strong>(trust)</strong> enforce bootstrap pins and remembered signer continuity by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/169">#169</a></li> <li>publish a packslip agent skill with releases by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/139">#139</a></li> <li>install packslip from packslip.sh with checksum-pinned scripts by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/174">#174</a></li> <li>publish packslip as a multi-arch container image on ghcr.io by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/179">#179</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jdx/packslip/commit/22be7aeb840156291e1ae795ca37b36a2dc1969c"><code>22be7ae</code></a> chore: release v1.5.1 (<a href="https://redirect.github.com/jdx/packslip/issues/190">#190</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/039ef00382c2d7976d619a7a6526fd749fe4adc9"><code>039ef00</code></a> fix(install): create a missing extraction parent without group write (<a href="https://redirect.github.com/jdx/packslip/issues/189">#189</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/4318d5b89ecf6775bf2f2166d25bde9804c93ab5"><code>4318d5b</code></a> fix(install): install under a group-writable umask such as Debian's 002 (<a href="https://redirect.github.com/jdx/packslip/issues/188">#188</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/9d13171497c4dbb789c5a1dfb69c8eea2f1a3b20"><code>9d13171</code></a> docs: show the install script and container image in getting started (<a href="https://redirect.github.com/jdx/packslip/issues/181">#181</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/224e7bcee0f9c43410f49cd23ef6eef0a35849a1"><code>224e7bc</code></a> chore: release v1.5.0 (<a href="https://redirect.github.com/jdx/packslip/issues/156">#156</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/1bc3cf5b22bd20c95cf913f23d3e4e291177704e"><code>1bc3cf5</code></a> feat(packaging): distribute native installers through signed APT and RPM repo...</li> <li><a href="https://github.com/jdx/packslip/commit/aeee4fd129f2fdb2e7d212e551d3ff22ff174f26"><code>aeee4fd</code></a> feat(packaging): build the installer offline with distro Rust toolchains (<a href="https://redirect.github.com/jdx/packslip/issues/186">#186</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/31f10536384c5783a5fd11a6ec0745e107117d61"><code>31f1053</code></a> test(compatibility): retain a released verifier baseline and publish support ...</li> <li><a href="https://github.com/jdx/packslip/commit/e5295a441a19acd293856a175e1dc67282a93246"><code>e5295a4</code></a> feat(install): bootstrap authenticated releases in user and system scopes (<a href="https://redirect.github.com/jdx/packslip/issues/184">#184</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/ae8bd77d82464fad03c1b67c6bfeed0e70902ae4"><code>ae8bd77</code></a> feat(install): check selected artifact host requirements (<a href="https://redirect.github.com/jdx/packslip/issues/177">#177</a>)</li> <li>Additional commits viewable in <a href="https://github.com/jdx/packslip/compare/87479dfc6443253dff69601cace5fc6ea07e6df5...22be7aeb840156291e1ae795ca37b36a2dc1969c">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
7024f9b31f |
ci: upgrade Tend and install Codecov uploaders from PyPI (#4369)
Upgrade the nine generated Tend workflows to 0.3.9. Repository setup now checks the Actions event policy needed for GitHub’s November 2 `pull_request_target` restriction; the active policy is scoped to `.github/workflows/tend-review.yaml` and its declared event. Install the Codecov CLI for coverage and test-result uploads from PyPI at 11.3.1 using the action’s supported `use_pypi` input. The coverage run failed twice, and test-result uploads silently failed under their existing soft-failure policy, because `cli.codecov.io` terminated the TLS handshake before the uploader downloaded. PyPI installation avoids that endpoint while preserving report artifacts, tokens, and each uploader’s existing failure policy. This uses the [action’s package-install path](https://github.com/codecov/codecov-action/blob/v7.1.1/dist/codecov.sh#L67), which replaces its standalone binary and GPG validation with PyPI package distribution. Validation: the published Tend generator reproduces every generated workflow; administrator event-policy check passes; the Rust suite (5,071 tests), doctests, docs build, clippy, workflow lint, and pre-commit checks pass. Both live uploader jobs install `codecov-cli` 11.3.1 successfully. Ingestion currently fails after request retries in CI; independent strict TLS checks show that `ingest.codecov.io` serves an expired certificate. The runner logs expose the request failures, without the underlying TLS exception, and uploads remain unavailable. Coverage computation completed and its report is retained as a GitHub Actions artifact; all other PR checks passed. The repository owner explicitly authorized landing without waiting for Codecov recovery. This is a one-time exception for the service failure: TLS validation, upload failure gates, and branch protection remain unchanged. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
b858fe7225 |
ci: bump pinned worktrunk to 0.80.0 (#4365)
Weekly CI pin bump: `worktrunk` `=0.79.0` → `=0.80.0`, at three sites (`ci.yaml` ×2, `nightly.yaml`). This is the `wt` that runs the suite (`wt hook pre-merge`) on all three platforms, so it has its own PR: this PR's CI matrix is the only place the bump gets tested. This week's other drifted pins (cargo-insta, and the MSRV/toolchain move to 1.98) are in their own PRs. Compatibility: worktrunk 0.80.0 declares `rust-version = 1.97`, which the pinned toolchain (`1.97.0`) satisfies. Neither of 0.80.0's two breaking changes reaches CI, which calls `wt` only as `wt hook pre-merge --yes <filters>`. They are git commit hooks running on a detached `HEAD` during a `wt merge`/`wt step squash` squash, and the `branch` field of `wt config state logs --format=json`; CI invokes neither. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
c911510774 |
ci: bump cargo-insta pin to 1.49.0 (#4366)
Weekly CI pin bump: `cargo-insta` `=1.48.0` → `=1.49.0` in `.github/actions/test-setup/action.yaml` and `.github/actions/tend-setup/action.yaml`, and `INSTA_VERSION` in `.codex/cloud.sh`, which is kept level with `test-setup`. `test-setup` feeds the test job on Linux, macOS, and Windows, so this bump has its own PR and its CI matrix is the test of it. Compatibility: cargo-insta 1.49.0 declares `rust-version = 1.66.0`, well under the pinned `1.97.0` toolchain. Its one CLI behavior change is that `cargo insta test --all-targets --test-runner nextest` no longer runs doctests; the `insta` pre-merge step in `.config/wt.toml` doesn't pass `--all-targets`, so it is unaffected. This bumps only the CLI; the `insta` library version stays with `Cargo.lock`. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
3561d5f07e |
chore: update tend workflows (0.3.5 → 0.3.7) (#4362)
Regenerates the Tend workflows with tend 0.3.7 (from 0.3.5). The effect for this repo: the generated workflows now pin third-party actions and `uv` to commits and checksums, and the bot's sessions pick up 0.3.6–0.3.7's skill and runner fixes. No `.config/tend.yaml` change was needed. What changes for worktrunk: - **Supply-chain pinning** — `actions/checkout` and `astral-sh/setup-uv` are pinned to commit SHAs (version kept as a comment), and the `uv` download (bumped to 0.12.22) is verified against a per-arch checksum (max-sixty/tend#1463). - **Mention prompt moves into a skill** — `tend-mention` now invokes `/tend-ci-runner:mention` and passes only the triggering event; the per-event "read the context, respond, make changes" instructions that were inlined in the workflow now live in the skill. - **`fetch-tags: true` is dropped from checkouts.** Every Tend checkout uses `fetch-depth: 0`, which already fetches all tags, so `build.rs`'s `git describe` still sees them. - **CI polling no longer waits on a job held for environment approval** (max-sixty/tend#1473), and nightly reads the last successful run more robustly so a cached listing can't widen its review range (max-sixty/tend#1468). - **Triage opens a PR when a maintainer is reasonably likely to merge it** rather than defaulting to a comment (max-sixty/tend#1471), and repair sessions resume unfinished bot work from the live PR state (max-sixty/tend#1479). - Claude Code is bumped to 2.1.288 (max-sixty/tend#1491). Full upstream diff: https://github.com/max-sixty/tend/compare/0.3.5...0.3.7 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
11fc85b50f |
chore: bump taiki-e/install-action from 2.87.21 to 2.87.22 (#4338)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.21 to 2.87.22. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.22</h2> <ul> <li> <p>Update <code>typos@latest</code> to 1.50.3.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.5.8.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.4.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.16.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.28.0.</p> </li> <li> <p>Update <code>gungraun-runner@latest</code> to 0.20.0.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.5.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.10.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.24.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.22] - 2026-09-29</h2> <ul> <li> <p>Update <code>typos@latest</code> to 1.50.3.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.5.8.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.4.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.16.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.28.0.</p> </li> <li> <p>Update <code>gungraun-runner@latest</code> to 0.20.0.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.5.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.10.</p> </li> <li> <p>Update <code>cargo-binstall@latest</code> to 1.24.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/83ac0ad63c0167e6f06796fab0fce28db1bf3db0"><code>83ac0ad</code></a> Release 2.87.22</li> <li><a href="https://github.com/taiki-e/install-action/commit/33ae788fe54853b371c41a6b54902a1d5b9611a8"><code>33ae788</code></a> Update <code>kache@latest</code> to 0.28.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/fe1dc9080218eed6788fc5a9007111e3b4c385f5"><code>fe1dc90</code></a> Update uv manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/ab1690bc222d9df33ee77aa61c817f37056c443e"><code>ab1690b</code></a> Update <code>typos@latest</code> to 1.50.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/e8f30886845956cfcb811e7256fcaf440deded6c"><code>e8f3088</code></a> Update <code>tombi@latest</code> to 1.5.8</li> <li><a href="https://github.com/taiki-e/install-action/commit/5016a80eb65a7b5b3ca6131006993010a4ade00a"><code>5016a80</code></a> Update <code>prek@latest</code> to 0.5.4</li> <li><a href="https://github.com/taiki-e/install-action/commit/71fcea0ef3de9012d71ed2018862e1e5bc60d282"><code>71fcea0</code></a> Update <code>mise@latest</code> to 2026.9.16</li> <li><a href="https://github.com/taiki-e/install-action/commit/194a94336f04b4ddaddc298dc0a8acc6490306a5"><code>194a943</code></a> Update <code>kache@latest</code> to 0.27.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/a681fbe5975aa9e5d7889860c2b50ffb48a52ad8"><code>a681fbe</code></a> Update <code>gungraun-runner@latest</code> to 0.20.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/8422291bd428284eca380fffd8b716c110d8d57b"><code>8422291</code></a> Update <code>cargo-tarpaulin@latest</code> to 0.37.5</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.21...v2.87.22">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
e9bfc368f4 |
chore: update tend workflows (0.3.4 → 0.3.5) (#4324)
Upgrades the generated Tend workflows from 0.3.4 to 0.3.5 ([compare](https://github.com/max-sixty/tend/compare/0.3.4...0.3.5)). The regenerated YAML changes little on its own: the action pin moves to `max-sixty/tend/claude@0.3.5`, and most of the behavior change arrives through the new action's bundled skills and scripts. What maintainers will notice: - **Bot PRs get their review findings applied.** The review workflow now decides whether to apply its own findings by who authored the PR, so a review on a bot-authored PR follows through with a fix instead of stopping at the comment (max-sixty/tend#1433). - **Relayed PR-review mentions are named after the PR.** `tend-mention` runs triggered through `tend-mention-relay` now get the PR title as their run name rather than the event type, and the notifications poll uses that name to tell which PR a live run is handling (max-sixty/tend#1450). The relay job also skips when `TEND_ENABLED` is `false`, instead of dispatching a run that does nothing (max-sixty/tend#1452). - **CI waits run to completion instead of a fixed cap.** CI polling and integration-test waits now wait for checks to settle instead of timing out at about 9 minutes, so a slow matrix reports its real result rather than "unverified" (max-sixty/tend#1448, max-sixty/tend#1451). - **Fewer truncated listings.** Pagination now reads every page of notifications, failed-run jobs, and workflow listings (max-sixty/tend#1435, max-sixty/tend#1442, max-sixty/tend#1457). The inline pagination helpers in `tend-mention` and `tend-notifications` now use `gh api --paginate --slurp`. - **Weekly dependency review matches Dependabot and Renovate PRs again.** It now matches on the `app/…` author login that `gh` reports (max-sixty/tend#1441). - **Nightly and review behavior.** Repo overlays can now skip advisory checks, review findings are ranked by severity, and the nightly issue sweep rotates across issues (max-sixty/tend#1450). `ci-fix` recurrence comments now lead with what changed (max-sixty/tend#1446). Also bumps the pinned `uv` from 0.12.17 to 0.12.19 in the pre-check steps. `.config/tend.yaml` has no model pin, so there was no model to update. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
28cc4d14cc |
chore: bump taiki-e/install-action from 2.87.20 to 2.87.21 (#4318)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.20 to 2.87.21. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.21</h2> <ul> <li> <p>Update <code>wasm-bindgen@latest</code> to 0.2.129.</p> </li> <li> <p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.3.</p> </li> <li> <p>Update <code>wasmtime@latest</code> to 49.0.1.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.19.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.13.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.7.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.21] - 2026-09-26</h2> <ul> <li> <p>Update <code>wasm-bindgen@latest</code> to 0.2.129.</p> </li> <li> <p>Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.3.</p> </li> <li> <p>Update <code>wasmtime@latest</code> to 49.0.1.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.19.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.13.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.7.0.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/4cef1412cce204788f482e778a0b9187f9626a29"><code>4cef141</code></a> Release 2.87.21</li> <li><a href="https://github.com/taiki-e/install-action/commit/133135e7fd1570baff8964a044bcf0d2147fc57a"><code>133135e</code></a> Update <code>wasm-bindgen@latest</code> to 0.2.129</li> <li><a href="https://github.com/taiki-e/install-action/commit/8589241798155a8c0c86c7c0ae4f642a90a698e1"><code>8589241</code></a> Update <code>protoc-gen-connect-openapi@latest</code> to 0.27.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/95e5bbc4a58633e12ebefd904f798c1eb76c18f7"><code>95e5bbc</code></a> Update wasmtime manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/48ce11d4f97676e64a76a3dc4b83a4f59245b702"><code>48ce11d</code></a> Update <code>wasmtime@latest</code> to 49.0.1</li> <li><a href="https://github.com/taiki-e/install-action/commit/368e6617a899743920fa751bb5d414b6f0352cc0"><code>368e661</code></a> Update wasm-bindgen manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/57f22a457e27d10a13bfcaee43e03dff1c20dedd"><code>57f22a4</code></a> Update <code>uv@latest</code> to 0.12.19</li> <li><a href="https://github.com/taiki-e/install-action/commit/888634e2727c1021a94ebfac9a2d266109a366b8"><code>888634e</code></a> Update typos manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/3bcab01fb9790f533b19647e60396514a9d08f96"><code>3bcab01</code></a> Update protoc-gen-connect-openapi manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/947e90eb285641d8325cc2d55ae24bd51d5c6b8a"><code>947e90e</code></a> Update <code>mise@latest</code> to 2026.9.13</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.20...v2.87.21">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
8f7bfcd0f4 |
chore: bump taiki-e/install-action from 2.87.18 to 2.87.20 (#4310)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.18 to 2.87.20. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.20</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.18.</p> </li> <li> <p>Update <code>cargo-shear@latest</code> to 1.14.0.</p> </li> </ul> <h2>2.87.19</h2> <ul> <li> <p>Update <code>wasmtime@latest</code> to 49.0.0.</p> </li> <li> <p>Update <code>cargo-shear@latest</code> to 1.13.5.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.146.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.20] - 2026-09-24</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.18.</p> </li> <li> <p>Update <code>cargo-shear@latest</code> to 1.14.0.</p> </li> </ul> <h2>[2.87.19] - 2026-09-23</h2> <ul> <li> <p>Update <code>wasmtime@latest</code> to 49.0.0.</p> </li> <li> <p>Update <code>cargo-shear@latest</code> to 1.13.5.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.146.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/9983c65e42da123ff25d1f78505eb6de315aa172"><code>9983c65</code></a> Release 2.87.20</li> <li><a href="https://github.com/taiki-e/install-action/commit/a66aca167f47497a79cdceeb83007ee4f11dbb54"><code>a66aca1</code></a> Update <code>uv@latest</code> to 0.12.18</li> <li><a href="https://github.com/taiki-e/install-action/commit/c69925a6db5d3891e00848e98dcbbdd810bb1a67"><code>c69925a</code></a> Update kingfisher manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/60b4ac9d51266f25e10b6638a4cfb5e6ed5ef31f"><code>60b4ac9</code></a> Update <code>cargo-shear@latest</code> to 1.14.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/7623a79cdfecb99d681017af368ca353d9f49bb5"><code>7623a79</code></a> Release 2.87.19</li> <li><a href="https://github.com/taiki-e/install-action/commit/e184dffea53be6d25cf5fbd37db3bb12b8d70f3d"><code>e184dff</code></a> Update <code>wasmtime@latest</code> to 49.0.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/8da1ba78ea1e003a87a95bba7ed3312e28c8ec68"><code>8da1ba7</code></a> Update uv manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/c8d1bf9fde2c971ee65bb81bdc6ab910e7fe1cea"><code>c8d1bf9</code></a> Update <code>cargo-shear@latest</code> to 1.13.5</li> <li><a href="https://github.com/taiki-e/install-action/commit/108c6509a3580c3eb9daf4a4351247b9cde762b7"><code>108c650</code></a> Update <code>cargo-nextest@latest</code> to 0.9.146</li> <li>See full diff in <a href="https://github.com/taiki-e/install-action/compare/v2.87.18...v2.87.20">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
f2996ba5c0 | ci(release): publish a signed packslip with each release (#4301) | ||
|
|
f9dc3e3dc2 |
ci: bump Nushell pin to 0.116.0 (#4300)
Weekly CI pin bump: Nushell `0.115.1` → `0.116.0`, the latest [`nushell/nushell` release](https://github.com/nushell/nushell/releases/tag/0.116.0) (published 2026-09-26). Seven sites move together: - the five `hustcer/setup-nu` inputs: `coverage.yaml`, `benchmarks.yaml`, `nightly.yaml`, and `.github/actions/{test,tend}-setup/action.yaml` - `NU_VERSION` in `.codex/cloud.sh`, which the weekly checklist keeps level with `test-setup` - `NU_VERSION` in `Taskfile.yaml`'s `setup-web` The `nu-0.116.0-x86_64-unknown-linux-gnu.tar.gz` asset that `cloud.sh` and `setup-web` download is published on the release. This is in its own PR because Nushell's version moves PTY snapshots under `--all-features`, and this PR's CI is the only place the bump is tested on macOS and Windows. The release's one breaking change that touches this repo is the unified completer input ([nushell/nushell#18791](https://github.com/nushell/nushell/pull/18791)). `templates/nushell.nu` already handles it: #4297 moved the completer to the new `place` input, so 0.116 no longer warns when the integration is sourced. Locally, with 0.116.0 on `PATH`, the `shell` integration-test subset gives the same results as with 0.115.1: 193 passed, and the same 16 failures, which are sandbox-environment snapshot failures present on main. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
14af21f23c |
ci: bump pinned worktrunk to 0.79.0 (#4298)
Weekly CI pin bump: `worktrunk` `=0.78.0` → `=0.79.0`, at three sites (`ci.yaml` ×2, `nightly.yaml`). This is the `wt` that runs the suite (`wt hook pre-merge`) on all three platforms, so it has its own PR: this PR's CI matrix is the only place the bump gets tested. This week's other drifted pins (cargo-nextest and Nushell) are in their own PRs. Compatibility: worktrunk 0.79.0 declares `rust-version = 1.97`, which matches the pinned toolchain (`rust-toolchain.toml` channel `1.97.0`). Neither of 0.79.0's two breaking changes reaches CI. CI calls `wt` only as `wt hook pre-merge --yes <filters>`. The breaking changes are to `wt switch --no-cd -x` (the program now runs in the new worktree) and to `wt merge`/`wt step rebase`, which now pass `--no-update-refs`. CI invokes none of those commands. <details><summary>Weekly checks that found no drift</summary> - **MSRV/toolchain**: current stable is `1.98.1`, so latest−1 is `1.97`, which `Cargo.toml`, `tests/helpers/wt-perf/Cargo.toml`, and `rust-toolchain.toml` already pin. The `nightly-2026-08-01` pins in `nightly.yaml` are about 8 weeks old, inside the three-month window. With no toolchain change, `flake.lock` needed no refresh. - **Other `cargo-install` pins**: `cargo-affected` 0.4.1, `cargo-insta` 1.48.0, `cargo-llvm-cov` 0.9.1, `cargo-msrv` 0.19.3, `cargo-udeps` 0.1.61, and `lychee` 0.24.2 all match their current crates.io releases. - **Codex Cloud tools**: PowerShell `7.6.6` is still the latest `PowerShell/PowerShell` release. `cloud.sh`'s cargo-nextest and Nushell pins move in the sibling PRs. - **Runner images**: `ubuntu-24.04`, `macos-26`, and `windows-2025` each still match their `-latest` label in the `actions/runner-images` table, and `ubuntu-24.04-arm` and `macos-26-intel` follow those rows. Xcode 27 is still badged preview. - **`dependabot.yaml` typescript ignore**: `@astrojs/check` still declares `typescript` `^5.0.0 || ^6.0.0`, so the major-version ignore entry stays (#3877). - **LLM model pins**: `claude-haiku-4.5` is still the current Haiku, and `gpt-6-luna` is what the Codex models page calls "our most efficient model". - **Statusline cache-check**: clean. `wt config state logs profile` reports `same_context_duplicates: []` on a `wt list statusline --format=claude-code` render. - **Agent integration surfaces**: nothing to flag. Claude Code 2.1.280–2.1.283 made no statusline schema change and no `WorktreeCreate`/`WorktreeRemove` change. Its new `claude plugin validate` checks (marketplace names it can't install, unquoted `${CLAUDE_PLUGIN_ROOT}` in shell-form hooks) pass for our manifest: the marketplace and plugin are both named `worktrunk`, and every hook quotes `"$CLAUDE_PLUGIN_ROOT/..."`. Codex `rust-v0.156.x`–`0.157.1`, Gemini CLI `v0.61.0`, and OpenCode `v1.18.32` change nothing in the marketplace, extension, or plugins API. - **README date stamp**: already September 2026. - **Dependency PRs**: none open. </details> Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
010821c519 |
ci: bump cargo-nextest pin to 0.9.146 (#4299)
Weekly CI pin bump: cargo-nextest `=0.9.145` → `=0.9.146`. It moves in four places: `coverage.yaml`, `.github/actions/test-setup/action.yaml`, `.github/actions/tend-setup/action.yaml`, and `NEXTEST_VERSION` in `.codex/cloud.sh`, which the weekly checklist keeps level with `test-setup`. The `cargo-nextest-0.9.146-x86_64-unknown-linux-gnu.tar.gz` asset that `cloud.sh` downloads is published on the release. Compatibility: 0.9.146 declares `rust-version = 1.91`, below the pinned `1.97.0` toolchain. The [release](https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.146)'s only change is updating the `chacha20` and `der` dependencies to non-yanked versions, so no test-runner behavior changes. The `worktrunk` and Nushell pins also drifted this week, and each has its own PR. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
570463bc58 |
ci(affected): stop shallowing the full clone before computing the merge-base (#4294)
The `affected tests` job computes its cache key with `git merge-base origin/main "$PR_HEAD"`, but first runs `git fetch --no-tags --depth=200 origin main`. That fetch runs on top of a `fetch-depth: 0` checkout, and a `--depth` fetch into a full clone makes it shallow: git writes `.git/shallow` and grafts main's history at 200 commits. For a PR whose fork point is more than 200 commits behind main, which is about three weeks of main here, `merge-base` finds nothing and the step exits 1. The job is advisory, so the run stays green, but that PR loses its affected-tests signal. The graft also cuts off older cached `collect_sha` commits that `cargo affected run` expects to reach. `origin/main` is already complete from the checkout, so this PR deletes the fetch and leaves a comment explaining why it must not come back. <details><summary>Reproduction</summary> On a full `file://` clone with main 10 commits deep and a PR branched 7 commits back: ``` $ git merge-base origin/main $PR # before 5b9c202b1c76a05cb76d09e5551a4940c112c845 $ git fetch -q --no-tags --depth=3 origin main $ git rev-parse --is-shallow-repository true $ git merge-base origin/main $PR; echo exit=$? exit=1 ``` None of the last 100 PR runs of `affected.yaml` failed at this step; current PRs are based recently enough. This PR's own `affected tests` jobs exercise the step without the fetch. </details> This is a CI config change, so there is no regression test. The repro above is the evidence. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
ebb27e3bfe |
docs: remove redundant CLAUDE.md imports (#4287)
Claude Code reads the existing AGENTS.md files directly, so remove the nine one-line CLAUDE.md imports that duplicate them. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
e9065c95e3 |
chore: update tend workflows (0.3.3 → 0.3.4) (#4278)
Regenerates the tend workflows for tend 0.3.3 → 0.3.4. The diff here is the version stamp and the `max-sixty/tend/claude` action pin; the behavior changes ship in the action and bundled skills: - **Relayed review replies no longer re-surface.** After the bot answers a PR review relayed through `tend-mention-relay`, the action now marks the matching notification read, so the notifications sweep doesn't pick the same review up again (max-sixty/tend#1425). - **Triage replies to feature requests are shorter.** The triage skill stops opening its reply by restating that the requested feature doesn't exist yet (max-sixty/tend#1423). - **Codex subscription setup fixes** in `install-tend`: the refresh PAT setup is now repository-specific, and forced terminal color no longer breaks the refresh environment setup (max-sixty/tend#1421, max-sixty/tend#1424). These only matter when running tend on Codex, as #4240 proposes. No model pins in `.config/tend.yaml` changed. Full comparison: https://github.com/max-sixty/tend/compare/0.3.3...0.3.4 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
81fe614192 |
chore: update tend workflows (0.3.2 → 0.3.3) (#4266)
Regenerates the Tend workflows with tend 0.3.3 (from 0.3.2). The generated change is small: each workflow now pins `max-sixty/tend/claude@0.3.3`, and the `control_plane_owner: ""` input is gone from the action calls because 0.3.3 removed that input. What changes for this repo: - Control-plane CODEOWNERS may now name several independent users per path, and `tend check` and the runtime preflight verify each owner's access (max-sixty/tend#1413). The single `control_plane_owner` input it replaces is why that line leaves the generated workflows. - The bundled `poll_pr_checks.py` ends its output with a standalone verdict line, so sessions polling PR checks read the result more reliably (max-sixty/tend#1417). The 0.3.3 Codex subscription-refresh credential split (max-sixty/tend#1418) does not apply here: this repo runs the Claude harness. `.config/tend.yaml` has no model pins, and 0.3.3 changes no harness model default. Full upstream diff: [0.3.2...0.3.3](https://github.com/max-sixty/tend/compare/0.3.2...0.3.3) Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
f637b38f8a |
chore: bump taiki-e/install-action from 2.87.17 to 2.87.18 (#4263)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.17 to 2.87.18. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.18</h2> <ul> <li> <p>Update <code>oxfmt@latest</code> to 1.84.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.12.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.26.3.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.4.</p> </li> <li> <p>Update <code>cargo-rdme@latest</code> to 2.2.3.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.18] - 2026-09-22</h2> <ul> <li> <p>Update <code>oxfmt@latest</code> to 1.84.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.12.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.26.3.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.4.</p> </li> <li> <p>Update <code>cargo-rdme@latest</code> to 2.2.3.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/dfae9bf3d6f6c6f20ef4ebb3486c01a51341ff12"><code>dfae9bf</code></a> Release 2.87.18</li> <li><a href="https://github.com/taiki-e/install-action/commit/0fa03e11dbbecbf7f738c1520b5f904072e967b0"><code>0fa03e1</code></a> Update <code>oxfmt@latest</code> to 1.84.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/0f764f8542bc06f667d5c476a882a5d8c700bda4"><code>0f764f8</code></a> Update wasmtime manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/2fcc16d9654b876550e807eb6d74110e5f15e8ac"><code>2fcc16d</code></a> Update oxfmt manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/ad339b431da7c5195135aa78a202d134f8f54178"><code>ad339b4</code></a> Update <code>mise@latest</code> to 2026.9.12</li> <li><a href="https://github.com/taiki-e/install-action/commit/1162c3b5ca872aa734e30ad9beb1f9893682154a"><code>1162c3b</code></a> Update <code>kache@latest</code> to 0.26.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/9e2a27b88627b1c4ab8359ccb30ef5f4d26eba18"><code>9e2a27b</code></a> Update <code>cargo-tarpaulin@latest</code> to 0.37.4</li> <li><a href="https://github.com/taiki-e/install-action/commit/75426271fb2960533f8690f87ca80ad57258b12e"><code>7542627</code></a> Update cargo-shear manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/d9ff78f735e5577607192b3e3e31653e7d3825b2"><code>d9ff78f</code></a> Update <code>cargo-rdme@latest</code> to 2.2.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/1d72ff714fb73c4dea309d21c8aed1d156d9ab42"><code>1d72ff7</code></a> Update cargo-nextest manifest</li> <li>See full diff in <a href="https://github.com/taiki-e/install-action/compare/v2.87.17...v2.87.18">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
6be77f12c9 |
chore: bump astral-sh/setup-uv from 10.1.0 to 10.2.0 in /.github/actions/tend-setup (#4250)
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.1.0 to 10.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v10.2.0 🌈 Disable automatic cache saves for merge queues</h2> <h2>Changes</h2> <p>This release contains the known-checksum of the most recent uv releases and also disabled the uploading(saving) of the cache when in a merge queue since theses caches would almost never be used.</p> <h2>🚀 Enhancements</h2> <ul> <li>Disable automatic cache saves for merge queues <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1056">#1056</a>)</li> </ul> <h2>🧰 Maintenance</h2> <ul> <li>chore: update known checksums for 0.12.17 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1058">#1058</a>)</li> <li>chore: update known checksums for 0.12.16 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1057">#1057</a>)</li> <li>chore: update known checksums for 0.12.15 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1054">#1054</a>)</li> <li>chore: update known checksums for 0.12.14 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1053">#1053</a>)</li> <li>chore: update known checksums for 0.12.13 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1045">#1045</a>)</li> </ul> <h2>📚 Documentation</h2> <ul> <li>docs: update version references to v10.1.0 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1044">#1044</a>)</li> </ul> <h2>⬆️ Dependency updates</h2> <ul> <li>chore(deps): roll up Dependabot updates <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1059">#1059</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/c18668ad3cf93ea998bef934396af7bb5c839dc7"><code>c18668a</code></a> chore(deps): roll up Dependabot updates (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1059">#1059</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/ffe14763056ca34ecd158146a9fc7e144c8a2753"><code>ffe1476</code></a> chore: update known checksums for 0.12.17 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1058">#1058</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/f5548c55522a1db0af3c84f2af3d058bc9bc2de2"><code>f5548c5</code></a> chore: update known checksums for 0.12.16 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1057">#1057</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a761a4e9afd7b2f353ae020bd6d3a3af34c6c4d5"><code>a761a4e</code></a> Disable automatic cache saves for merge queues (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1056">#1056</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/3377a30666f438759955882b3eba6a92b2b29b12"><code>3377a30</code></a> chore: update known checksums for 0.12.15 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1054">#1054</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/dfb5f386776afcea37f271f3b656318d9949b9f1"><code>dfb5f38</code></a> chore: update known checksums for 0.12.14 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1053">#1053</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/45c121f982720f3bdf236c2ac06f126ca211949c"><code>45c121f</code></a> chore: update known checksums for 0.12.13 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1045">#1045</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/8073452fd4b566e886f04f731bcdbd8332b0b779"><code>8073452</code></a> docs: update version references to v10.1.0 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1044">#1044</a>)</li> <li>See full diff in <a href="https://github.com/astral-sh/setup-uv/compare/v10.1.0...v10.2.0">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
e99d4ff74e |
Move Tend tool setup to standard steps and update to 0.3.2 (#4249)
Move the Tend tool probe into standard setup and remove the deprecated sandbox_setup key. Regenerate the workflows with Tend 0.3.2; restricted merge policy preserves the current bot authority. The setup action continues to install the required tools, and a prior nightly run confirmed pre-commit reaches the agent PATH. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
268628f70f |
chore: update tend workflows (0.2.15 → 0.3.1) (#4243)
Regenerates the nine `tend-*.yaml` workflows from tend 0.3.1, up from 0.2.15. Behavior here is unchanged: the only substantive diff is two new action inputs, `merge: maintainer` and `control_plane_owner: ""`, both of which are the action's own defaults. `maintainer` is the merge authority this repo already runs under — the bot proposes, a maintainer merges. What the upgrade changes for this repo: - **`tend check` audits protected refs and credential environments more strictly** ([max-sixty/tend#1382](https://github.com/max-sixty/tend/pull/1382)). A protected branch must now restrict creation, update and deletion together rather than update alone, and the credential audit no longer treats a ref-qualified reusable workflow as this tree's copy. This repo does not clear the new bar yet — the nightly filed #4242 with the single ruleset gap and the remediation. - **Yolo merge mode exists, and is off** ([max-sixty/tend#1172](https://github.com/max-sixty/tend/pull/1172), [#1390](https://github.com/max-sixty/tend/pull/1390)). The new inputs are how a repo would opt into letting the bot merge its own PRs; leaving them at the defaults keeps the current arrangement, and the `merge: maintainer` value is what the mitmproxy cache step is now gated on. - **`review-runs` sees the whole night** ([max-sixty/tend#1377](https://github.com/max-sixty/tend/pull/1377)). Run listing now pages to the Actions ceiling instead of stopping at the first page, so a busy night's early runs stop falling out of the census; [#1374](https://github.com/max-sixty/tend/pull/1374) keeps each correction row's author alongside it. - **CI polling is bounded by elapsed time, not iteration count** ([max-sixty/tend#1376](https://github.com/max-sixty/tend/pull/1376), reinstating [#1371](https://github.com/max-sixty/tend/pull/1371) after [#1375](https://github.com/max-sixty/tend/pull/1375) reverted it). A settle loop against slow checks now stops on a sleep budget, so a long matrix can't quietly stretch a session. - **Install-test drift detection tightened** ([max-sixty/tend#1381](https://github.com/max-sixty/tend/pull/1381)): generator output a PR never committed now fails tend's own drift check, which is the check that makes a regeneration PR like this one trustworthy. Full comparison: [0.2.15...0.3.1](https://github.com/max-sixty/tend/compare/0.2.15...0.3.1). This PR does not touch `.config/tend.yaml`, whose `sandbox_setup:` key 0.3.1 now warns "will be refused in a later release". That migration is a separate change. #4240 overlaps this completely: it was generated with the same 0.3.1, so it carries the identical headers and the identical `merge: maintainer` / `control_plane_owner: ""` on the same lines, underneath a Claude → Codex harness swap. The only thing that distinguishes the two is which harness the action runs. Whichever lands first leaves the other conflicting on the eight `uses:` lines, resolved by regeneration rather than by hand. So this PR is worth landing on its own only for as long as the Codex cutover stays in draft — if that lands first, close this one. Verified by regenerating in the merged tree: `uvx tend@0.3.1 init` reproduces these nine files byte-for-byte, and the action declares `default: maintainer` and `default: ""` for the two new inputs at `0.3.1`, so neither changes behavior. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
e8b264c011 |
docs: trim repository agent guidance (#4246)
The repository guidance had grown into long implementation histories, especially in the plugin instructions surfaced by #4241. This trims the nine guidance files from 2,769 lines to 380, keeping active contracts and fragile workflows while moving enduring cache semantics into the owning module docstring and updating trace and feature-spec references. This follows #4245, which moved the guidance into `AGENTS.md`. The nine `CLAUDE.md` forwarding files remain in place. Verified with the plugin-layout and documentation-sync integration tests, `pre-commit`, JSON parsing for the updated feature specifications, and `git diff --check`. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
6502630366 |
docs: share project instructions through AGENTS.md (#4245)
Make `AGENTS.md` the canonical project instructions in nine directories. Each directory also has a one-line `CLAUDE.md` importing its adjacent `AGENTS.md`, so Claude Code loads the instructions even on accounts where native `AGENTS.md` support is gated off. The root `AGENTS.md` replaces the old symlink; ordinary files work on Windows checkouts without symlink support. References in source comments, CI, Clawpatch metadata, maintainer skills, and the demo fixture point to the canonical paths. I verified Claude Code's `@` import in a live isolated probe with tools disabled: a `CLAUDE.md` import loaded a marker found only in the imported file. The wrappers keep the existing Claude Code instruction-loading path while Codex reads `AGENTS.md` directly. Verified: `test_docs_are_in_sync`, `test_plugin_layout_is_consolidated`, `test_no_host_specific_paths_in_snapshots`, the docs production build, 20 built-site tests, Python compilation of the demo helper, JSON parsing of the feature metadata, and `git diff --check`. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
ccb32f0ca8 |
chore: bump taiki-e/install-action from 2.87.16 to 2.87.17 (#4237)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.16 to 2.87.17. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.17</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.17.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.169.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.5.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.25.0.</p> </li> <li> <p>Update <code>git-cliff@latest</code> to 2.14.2.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.3.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.9.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.17] - 2026-09-20</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.17.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.169.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.5.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.25.0.</p> </li> <li> <p>Update <code>git-cliff@latest</code> to 2.14.2.</p> </li> <li> <p>Update <code>cargo-tarpaulin@latest</code> to 0.37.3.</p> </li> <li> <p>Update <code>cargo-leptos@latest</code> to 0.3.9.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/94c31af3204a9f15ab40b35ad084410b905bbc73"><code>94c31af</code></a> Release 2.87.17</li> <li><a href="https://github.com/taiki-e/install-action/commit/475671fc114659712ce2ff4c1d94a927df34acaa"><code>475671f</code></a> Update <code>uv@latest</code> to 0.12.17</li> <li><a href="https://github.com/taiki-e/install-action/commit/eed0e36340db98284aecb38cec932175e66e08ea"><code>eed0e36</code></a> Update <code>release-plz@latest</code> to 0.3.169</li> <li><a href="https://github.com/taiki-e/install-action/commit/28baa71610ff9c6ca6f9c2238420167a40febe2d"><code>28baa71</code></a> Update <code>kingfisher@latest</code> to 2.5.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/2588b3fa536b03dd80a635cd335014a5a7fbd06c"><code>2588b3f</code></a> Update <code>kache@latest</code> to 0.25.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/0d4ca4ed781961f5ab749f0c9f822ff33177e1bf"><code>0d4ca4e</code></a> Update <code>git-cliff@latest</code> to 2.14.2</li> <li><a href="https://github.com/taiki-e/install-action/commit/b96f11eb0c9f8820d621c4b53579f5ad6045195e"><code>b96f11e</code></a> Update <code>cargo-tarpaulin@latest</code> to 0.37.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/18f77226f9e7299acf999113898461dc73e12132"><code>18f7722</code></a> Update <code>cargo-leptos@latest</code> to 0.3.9</li> <li>See full diff in <a href="https://github.com/taiki-e/install-action/compare/v2.87.16...v2.87.17">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
566f69cc4f |
chore(ci): delete list-recent-runs.sh, orphaned since the tend migration (#4231)
`.github/scripts/list-recent-runs.sh` has had no caller since March. It was extracted in #1302 to feed the `review-reviewers` skill ("Run `.github/scripts/list-recent-runs.sh` for recently completed Claude CI runs"), and #1676 moved that skill to the tend repo while replacing the hand-written Claude workflows with generated ones. The script survived the move; its only reference didn't. Nothing references it today — neither the repo (`git grep list-recent-runs` returns nothing outside the file itself) nor tend's bundled skills, which is where the calling skill now lives. The deletion empties `.github/scripts/`, so the directory goes with it. No test accompanies this: the change removes an unreferenced file and alters no behavior to regress. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
1f8461af1b |
chore: update tend workflows (0.2.14 → 0.2.15) (#4229)
Regenerates the nine `tend-*.yaml` workflows with tend 0.2.15 (from 0.2.14). The version bump and the `astral-sh/setup-uv` pin (v10.1.0 → v10.2.0, in the `tend-mention` and `tend-notifications` preflight jobs) are mechanical; one step actually moves, in `tend-mention.yaml`. **`tend-mention` measures its queue delay before checkout and setup.** The "Compute queue delay" step used to run after `actions/checkout` and `./.github/actions/tend-setup`, so the number it recorded was the wait for the job to start *plus* the several minutes this repo's setup action takes to install the Rust toolchain and sandbox tools. It now runs first, and the delay reports the queue wait alone ([max-sixty/tend#1365](https://github.com/max-sixty/tend/pull/1365)). Behavior that arrives inside the action rather than in these files, and that shows up in what the bot posts here: - **PR reviews lead with a finding.** A review body now opens with something actionable instead of restating the verdict GitHub already renders in its own header ([max-sixty/tend#1362](https://github.com/max-sixty/tend/pull/1362)), and a follow-up review scopes itself to what the latest push changed while still reading the whole PR ([max-sixty/tend#1368](https://github.com/max-sixty/tend/pull/1368)). - **Fewer self-directed fix rounds on bot PRs.** On a PR with no human author the review session applies its own findings; each further round now has to clear a higher bar, so a bot PR stops accumulating marginal follow-up commits ([max-sixty/tend#1366](https://github.com/max-sixty/tend/pull/1366)). - **`AGENTS.override.md` joins the pinned instruction paths.** Codex reads it in preference to `AGENTS.md`, so on a PR-derived checkout it is now restored from the base commit alongside `CLAUDE.md`, `AGENTS.md`, `.claude/`, and `.agents/` — a fork can no longer reach the session through that filename. The same release makes a restrict-updates ruleset a `tend check` requirement; this repo already satisfies it (`tend check` passes every line today) ([max-sixty/tend#1367](https://github.com/max-sixty/tend/pull/1367)). Full comparison: [0.2.14...0.2.15](https://github.com/max-sixty/tend/compare/0.2.14...0.2.15). Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
9e570007a3 |
chore: bump taiki-e/install-action from 2.87.15 to 2.87.16 (#4227)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.15 to 2.87.16. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.16</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.16.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.168.</p> </li> <li> <p>Update <code>protoc@latest</code> to 3.36.2.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.11.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.16] - 2026-09-19</h2> <ul> <li> <p>Update <code>uv@latest</code> to 0.12.16.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.168.</p> </li> <li> <p>Update <code>protoc@latest</code> to 3.36.2.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.11.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/9114bf4d891761788c546334fd37538eae1bf8b3"><code>9114bf4</code></a> Release 2.87.16</li> <li><a href="https://github.com/taiki-e/install-action/commit/bef0ddf2a7e45573907045d6d2e764dc0b552ec4"><code>bef0ddf</code></a> Update <code>uv@latest</code> to 0.12.16</li> <li><a href="https://github.com/taiki-e/install-action/commit/36f0b2e823393a7be9f1979cac5ddeae9d610fdf"><code>36f0b2e</code></a> Update <code>release-plz@latest</code> to 0.3.168</li> <li><a href="https://github.com/taiki-e/install-action/commit/d2e5cdac9618886e1720537b4a0a62115b877ae6"><code>d2e5cda</code></a> Update <code>protoc@latest</code> to 3.36.2</li> <li><a href="https://github.com/taiki-e/install-action/commit/257b23d8dab2f8e29e91dac29e711cb0fbcd03b9"><code>257b23d</code></a> Update <code>mise@latest</code> to 2026.9.11</li> <li><a href="https://github.com/taiki-e/install-action/commit/35afe7990d2eef47d2b201a4a6ae4f6e298d4826"><code>35afe79</code></a> Update kingfisher manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/64a0f280bfe9ae5d011a89695ab3e0e3619e5fe8"><code>64a0f28</code></a> Update kache manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/2df4de46f5f1f3b13bcca17f0cf1f02d131d3d4b"><code>2df4de4</code></a> Update git-cliff manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/c5119b68d50710c31eb04b4cc7de00926f51ed77"><code>c5119b6</code></a> Update cargo-leptos manifest</li> <li>See full diff in <a href="https://github.com/taiki-e/install-action/compare/v2.87.15...v2.87.16">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
a73730c9af |
docs(ci): correct the tend sandbox model for 0.2.14's copy-on-write view (#4224)
tend 0.2.14 (landed today in #4222) moved the agent off Anthropic Sandbox Runtime and onto a hardened systemd unit over a copy-on-write view of the job's own checkout and home. Four files here still describe the 0.2.5–0.2.13 arrangement they were written for, and their central claims are now observably false from inside a session. That matters because `.github/CLAUDE.md` and `running-tend` are what an agent reads before touching CI: told the runner's home is unreadable, it keeps building hand-offs nothing needs and rules out a cache that would now work. Comments and instructions only — no step, key, or behavior changes. ## What stopped being true Probed from tend 0.2.14 sessions: | Documented claim | Observed | | --- | --- | | Agent PATH rewrites a leading `/home/runner` to `/home/tend-sandbox` | `$HOME` is `/home/runner`, and PATH entries resolve there | | The agent builds in a disposable `/tmp` clone | cwd is `/home/runner/work/worktrunk/worktrunk`, the runner's own checkout | | Sandbox Runtime denies reads across the runner's home and checkout | `~/.cargo`, `~/.rustup/toolchains` and `~/.cargo-install` all read fine | | The cargo tools reach the agent through `/usr/local/bin` | `which -a cargo-insta` lists `/home/runner/.cargo-install/cargo-insta/bin/cargo-insta` first, `/usr/local/bin` second | | `.config/tend.yaml`'s probe runs inside the sandbox, and a missing tool files a tend-outage issue | 0.2.14's generator emits the block as an ordinary runner step *before* `max-sixty/tend/claude`, and the filing is `report_failure.py`, a step *inside* that action under `if: failure()` — so a probe failure skips it and leaves only its `::error::` annotation | | `running-tend`: the weekly `nix` commands fail with a permission error | `nix store info` reports `cannot create Unix domain socket: Address family not supported by protocol` | | `running-tend`: `-home-runner-work-worktrunk-worktrunk/` "appears only in runs predating the bump" | This session's logs are under `/home/tend-sandbox/.claude/projects/-home-runner-work-worktrunk-worktrunk/` — the prefix is back | One claim in the same paragraphs was checked and kept: `nix` still cannot reach the daemon, so `socket(AF_UNIX, …)` is blocked under the systemd unit too, and the weekly `flake.lock` refresh still needs max-sixty/tend#1197. Only the errno was wrong, in two places — `.github/actions/tend-setup/action.yaml` said `EPERM` and `running-tend` said "a permission error"; both now carry the message the probe actually prints. ## What this deliberately leaves alone - **`sandbox_setup:` stays.** #4222 gave the reason: keeping the key means a release reverting 0.2.14 still finds it. The comment above the block now says so, so a later sweep reads it as a deliberate hold rather than drift to fix. Its closing probe is still worth its place — it asserts the five tools the pre-merge gate needs, whichever step installed them, and fails the job naming the one that went missing. - **The `/usr/local/bin` publish step stays**, re-described as the second copy of those binaries it now is rather than the only route. ## One follow-up this opens but does not take `tend-setup` carries no `rust-cache` step because a restored `~/.cargo` and `<checkout>/target` were unreachable and at the wrong path. Both are now reachable at the path a restore writes them to, so tend sessions build cold only because nothing restores them. The comment moves from "blocked until max-sixty/tend#1198" to "a measurement", but no cache is added here: that is a behavior change with a real download cost across eight workflows, and it wants its own PR with numbers. <details><summary>Probe output</summary> ``` $ echo "HOME=$HOME"; whoami; pwd HOME=/home/runner tend-sandbox /home/runner/work/worktrunk/worktrunk $ which -a cargo-insta /home/runner/.cargo-install/cargo-insta/bin/cargo-insta /usr/local/bin/cargo-insta $ ls ~/.rustup/toolchains stable-x86_64-unknown-linux-gnu $ which -a pre-commit /home/runner/.local/bin/pre-commit $ ls -d ~/.claude/projects/*/ ls: cannot access '/home/runner/.claude/projects/*/': No such file or directory $ ls -d /home/tend-sandbox/.claude/projects/*/ /home/tend-sandbox/.claude/projects/-home-runner-work-worktrunk-worktrunk/ $ nix store info Store URL: daemon error: cannot create Unix domain socket: Address family not supported by protocol ``` The probe-ordering claim comes from the generated workflows rather than a runtime probe: `.github/workflows/tend-review.yaml` puts the `sandbox_setup:` block between `uses: ./.github/actions/tend-setup` and `uses: max-sixty/tend/claude@0.2.14`, and `claude/action.yaml` at tag 0.2.14 runs `report_failure.py` as its own `if: failure()` step. </details> --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
8a48a37660 |
chore: update tend workflows (0.2.13 → 0.2.14) (#4222)
Regenerates the tend workflows with tend 0.2.14 ahead of the nightly update, to trial the release here. 0.2.14 runs the agent in a hardened systemd unit instead of Anthropic Sandbox Runtime, over a copy-on-write view of the job's own checkout and home (max-sixty/tend#1346, max-sixty/tend#1354). `sandbox_setup:` is deprecated, so `init` now runs its commands as an ordinary step after `setup:`, as the runner user, and the agent sees what they install through the view. `.config/tend.yaml` keeps the key for now, so a release that reverts 0.2.14 would still find it. Release notes: https://github.com/max-sixty/tend/releases/tag/0.2.14 > _This was written by Claude Code on behalf of max-sixty_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Maximilian Roos <maximilian@MacBook-Pro-2.local> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|
|
c5e17139a8 |
chore: update tend workflows (0.2.11 → 0.2.13) (#4215)
Regenerates the `tend-*` workflows with tend 0.2.13 (from 0.2.11). Mechanically the diff is the action pin `max-sixty/tend/claude@0.2.11` → `@0.2.13` in the eight workflows that run the agent, the `astral-sh/setup-uv` pin `0.12.13` → `0.12.17` in the two that install uv directly (`tend-mention`, `tend-notifications`), and a regenerated header comment in all nine. The upgrade that matters for this repo is in CI polling. `poll_pr_checks.py` previously treated any gating check that settled without a red conclusion as green — so a required check belonging to a **cancelled** or **stale** run, or a `COMPLETED` check carrying no conclusion at all, let the bot report a PR as green when nothing had actually verified it. 0.2.13 splits those out as `unverified` and gives `poll` a distinct exit code for them (max-sixty/tend#1323). Practically: fewer "checks went green" claims on PRs whose required jobs were cancelled, at the cost of some polls ending unverified rather than green. The rest, in rough order of how visible it is here: - **Sandbox reliability** — the sandbox runtime now retries past a transient bridge-socket failure at launch (max-sixty/tend#1327). That failure is one of the shapes that produces a `tend-outage` issue, so it should show up as fewer of those. - **Sandbox environment** — root `/tmp` is writable inside the sandbox (max-sixty/tend#1324); the `run-tend` skill's note that it was read-only is gone. This repo's `running-tend` skill still restates that note, so it goes stale when this merges — I'll follow up separately rather than mix a skill edit into the generated-workflow diff. - **Instruction-path pinning** — the `run-tend` skill's description of which paths get restored from the PR base, and on which events, was wrong in 0.2.11; `.agents/` is now named alongside `.claude/`, and the event list is corrected (max-sixty/tend#1311). The restore behavior itself is unchanged. - **Auth hygiene** — the bot's claude.ai account is kept out of CI sessions (max-sixty/tend#1328). - **Harness pins** — claude-code 2.1.278 (max-sixty/tend#1330), uv 0.12.17 (max-sixty/tend#1331). `.config/tend.yaml` pins no model, so the harness-default check found nothing to adjust. Full comparison: https://github.com/max-sixty/tend/compare/0.2.11...0.2.13 <details><summary>Copy-on-write sandbox view: landed and reverted within this range</summary> max-sixty/tend#1333 and max-sixty/tend#1334 moved the agent into the job's own checkout and home through a copy-on-write view; max-sixty/tend#1339 reverted both before 0.2.13. Nothing from that work is in this diff — noted so a later reader doesn't chase it out of the commit list. </details> Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
d462f9eb44 |
chore: bump taiki-e/install-action from 2.87.13 to 2.87.15 (#4211)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.13 to 2.87.15. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.15</h2> <ul> <li> <p>Update <code>syft@latest</code> to 1.52.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.10.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.4.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.23.1.</p> </li> <li> <p>Update <code>coreutils@latest</code> to 0.12.0.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.145.</p> </li> </ul> <h2>2.87.14</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.30.6.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.15.</p> </li> <li> <p>Update <code>typos@latest</code> to 1.50.2.</p> </li> <li> <p>Update <code>sccache@latest</code> to 0.18.0.</p> </li> <li> <p>Update <code>oxfmt@latest</code> to 1.83.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.9.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.3.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.22.0.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.5.14.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.15] - 2026-09-18</h2> <ul> <li> <p>Update <code>syft@latest</code> to 1.52.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.10.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.4.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.23.1.</p> </li> <li> <p>Update <code>coreutils@latest</code> to 0.12.0.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.145.</p> </li> </ul> <h2>[2.87.14] - 2026-09-17</h2> <ul> <li> <p>Update <code>vacuum@latest</code> to 0.30.6.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.12.15.</p> </li> <li> <p>Update <code>typos@latest</code> to 1.50.2.</p> </li> <li> <p>Update <code>sccache@latest</code> to 0.18.0.</p> </li> <li> <p>Update <code>oxfmt@latest</code> to 1.83.0.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.9.9.</p> </li> <li> <p>Update <code>kingfisher@latest</code> to 2.3.0.</p> </li> <li> <p>Update <code>kache@latest</code> to 0.22.0.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.5.14.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/4076c08d76dba979c11a7285295b0716c1d67908"><code>4076c08</code></a> Release 2.87.15</li> <li><a href="https://github.com/taiki-e/install-action/commit/f094888c5791ae387911f93453f99883b07e21d7"><code>f094888</code></a> Update uv manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/df9870f5d066ae12320fddfddc94d0a33a827c0e"><code>df9870f</code></a> Update <code>syft@latest</code> to 1.52.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/d432ab24a3d5e1a4c90d5d79dc75db5cca39349c"><code>d432ab2</code></a> Update release-plz manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/f2e9e6cfe93e0a85218642d16cb0211924c3a79e"><code>f2e9e6c</code></a> Update protoc manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/55468834f6c05f71d0252577556ae8db9209b7f6"><code>5546883</code></a> Update <code>mise@latest</code> to 2026.9.10</li> <li><a href="https://github.com/taiki-e/install-action/commit/6dfd42ab1ba4866ac60f829603c182c250acc5f3"><code>6dfd42a</code></a> Update <code>kingfisher@latest</code> to 2.4.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/5157ed3a9e5930980b523c09776d2ee117dfdd20"><code>5157ed3</code></a> Update <code>kache@latest</code> to 0.23.1</li> <li><a href="https://github.com/taiki-e/install-action/commit/78a18ea63bde66c8cfc44b49547da89159f6692c"><code>78a18ea</code></a> Update <code>coreutils@latest</code> to 0.12.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/b02e9c7b26f6b943d3c1b7c263caa72f85950d39"><code>b02e9c7</code></a> Update <code>cargo-nextest@latest</code> to 0.9.145</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.13...v2.87.15">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
fd183481a3 |
chore: bump clechasseur/rs-cargo from 5.0.8 to 5.1.0 (#4210)
Bumps [clechasseur/rs-cargo](https://github.com/clechasseur/rs-cargo) from 5.0.8 to 5.1.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/clechasseur/rs-cargo/releases">clechasseur/rs-cargo's releases</a>.</em></p> <blockquote> <h2>v5.1.0</h2> <p>New release supporting any Cargo-like tool, not just <code>cross</code> or <code>cargo-hack</code>. Also includes updated dependencies with security fixes.</p> <h2>What's Changed</h2> <ul> <li>chore(deps): bump js-yaml from 3.15.1 to 3.15.2 in the npm_and_yarn group across 1 directory by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/clechasseur/rs-cargo/pull/444">clechasseur/rs-cargo#444</a></li> <li>feat: add support for any Cargo-like tool, update dependencies by <a href="https://github.com/clechasseur"><code>@clechasseur</code></a> in <a href="https://redirect.github.com/clechasseur/rs-cargo/pull/446">clechasseur/rs-cargo#446</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/clechasseur/rs-cargo/compare/v5.0.8...v5.1.0">https://github.com/clechasseur/rs-cargo/compare/v5.0.8...v5.1.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/clechasseur/rs-cargo/commit/a12d4742fa9b832ccb29dc394a68ab577b0c9fb8"><code>a12d474</code></a> Merge pull request <a href="https://redirect.github.com/clechasseur/rs-cargo/issues/446">#446</a> from clechasseur/fix/update-deps</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/616591a16783f2dc66acebb6d44b1f17f3be6ba2"><code>616591a</code></a> chore: no need to install Rust for JS tests</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/fc708847eb212f6e0e9cd3c86f36cf9048c6b5d1"><code>fc70884</code></a> Merge remote-tracking branch 'origin/fix/update-deps' into fix/update-deps</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/6865ea83a8714d7b153bc2650cf45aaeb19b7f23"><code>6865ea8</code></a> feat: bump version to 5.1.0</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/d8a7778d7ed4fcc315ceda48017abb7acd960ba2"><code>d8a7778</code></a> chore: set <code>build-warnings: warn</code> to be able to test warnings</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/dc125d7fcbfcab3b2448ab8a10a7cc4bf696e7d0"><code>dc125d7</code></a> Merge remote-tracking branch 'origin/renovate/actions-rust-lang-setup-rust-to...</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/d292f7b8ad975dce5e03f59267ce2d0a3a292c51"><code>d292f7b</code></a> feat: update <code>@clechasseur/rs-actions-core</code> to 10.0.0</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/6a9d914da64ee73b2c6207a9f8b80ab6867f0e80"><code>6a9d914</code></a> fix: update dependencies</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/3d0012d8a793d6cf529b6836205fc13add233f60"><code>3d0012d</code></a> chore: ignore warning about <code>isolatedModules: false</code></li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/c7158e86c968466e17fc4a2d83175cfb53be1d84"><code>c7158e8</code></a> chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/444">#444</a>)</li> <li>Additional commits viewable in <a href="https://github.com/clechasseur/rs-cargo/compare/v5.0.8...v5.1.0">compare view</a></li> </ul> </details> <br /> [](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> |
||
|
|
1b5ecff967 |
chore: bump codecov/codecov-action from 7.1.0 to 7.1.1 (#4208)
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 7.1.0 to 7.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/codecov/codecov-action/releases">codecov/codecov-action's releases</a>.</em></p> <blockquote> <h2>v7.1.1</h2> <h2>What's Changed</h2> <ul> <li>chore(release): 7.1.1 by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1973">codecov/codecov-action#1973</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v7.1.0...v7.1.1">https://github.com/codecov/codecov-action/compare/v7.1.0...v7.1.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/codecov/codecov-action/commit/303a32d7a59b442fa8d48b6a1cc6825c09c847a5"><code>303a32d</code></a> chore(release): 7.1.1 (<a href="https://redirect.github.com/codecov/codecov-action/issues/1973">#1973</a>)</li> <li>See full diff in <a href="https://github.com/codecov/codecov-action/compare/v7.1.0...v7.1.1">compare view</a></li> </ul> </details> <br /> [](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> |