ci: bump the actions group across 1 directory with 8 updates

[dependabot]

Bumps the actions group with 8 updates in the / directory:

Package	From	To
bounded-systems/.github/.github/workflows/_claim-sweep.yml	14c1a9b3ade8bb6416f46c890eda21823647da09	2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445
bounded-systems/ci-workflows/.github/workflows/osv-scan.yml	0.1.4	0.1.5
bounded-systems/.github/.github/actions/broker-gh-token	99e88a0335519cb78be8a1b6623105613fa6aca1	2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445
bounded-systems/.github/.github/workflows/_pr-claim.yml	8a56f22f32bd007affbef503a4f1ac736c9aa52d	2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445
step-security/harden-runner	2.21.0	2.21.1
bounded-systems/mint/.github/workflows/release-provenance.yml	0.5.0	0.8.0
bounded-systems/.github/.github/workflows/repo-standard.yml	99e88a0335519cb78be8a1b6623105613fa6aca1	2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445
bounded-systems/mint/.github/workflows/version.yml	0.5.0	0.8.0

Updates bounded-systems/.github/.github/workflows/_claim-sweep.yml from 14c1a9b3ade8bb6416f46c890eda21823647da09 to 2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445

Commits

• 2cd9ebc _auto-merge: one reusable arming lane, minting through the broker (#387)
• b267ca5 fix(conformance): the publish step passed the snapshot through argv, and argv...
• 3e8ba03 feat(conformance): project which public repos call repo-standard, and how (#383)
• 0ee10a7 chore(burndown): add the kit and archive the 2026-09-03 Desk run (#378)
• af649d8 chore(bootstrap): pin 73805c56b738 and re-record digests (#376)
• 73805c5 verb-server: graph mode refuses a window, and three doc claims stop being fal...
• ed7c381 discoverability: assert the name a client must TYPE, not the one we store (#375)
• 6e32458 Re-roll the org Claude harness baseline (#370)
• 10582a2 pr-claim: when an issue is unreadable, say why and what to do (#369)
• 9d83046 org-repair.sh: canonical bytes, and a digest pin so it cannot drift silently ...
• Additional commits viewable in compare view

Updates bounded-systems/ci-workflows/.github/workflows/osv-scan.yml from 0.1.4 to 0.1.5

Commits

• fb7ca62 ci: bump the actions group across 1 directory with 3 updates (#34)
• See full diff in compare view

Updates bounded-systems/.github/.github/actions/broker-gh-token from 99e88a0335519cb78be8a1b6623105613fa6aca1 to 2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445

Commits

• 2cd9ebc _auto-merge: one reusable arming lane, minting through the broker (#387)
• b267ca5 fix(conformance): the publish step passed the snapshot through argv, and argv...
• 3e8ba03 feat(conformance): project which public repos call repo-standard, and how (#383)
• 0ee10a7 chore(burndown): add the kit and archive the 2026-09-03 Desk run (#378)
• af649d8 chore(bootstrap): pin 73805c56b738 and re-record digests (#376)
• 73805c5 verb-server: graph mode refuses a window, and three doc claims stop being fal...
• ed7c381 discoverability: assert the name a client must TYPE, not the one we store (#375)
• 6e32458 Re-roll the org Claude harness baseline (#370)
• 10582a2 pr-claim: when an issue is unreadable, say why and what to do (#369)
• 9d83046 org-repair.sh: canonical bytes, and a digest pin so it cannot drift silently ...
• Additional commits viewable in compare view

Updates bounded-systems/.github/.github/workflows/_pr-claim.yml from 8a56f22f32bd007affbef503a4f1ac736c9aa52d to 2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445

Commits

• 2cd9ebc _auto-merge: one reusable arming lane, minting through the broker (#387)
• b267ca5 fix(conformance): the publish step passed the snapshot through argv, and argv...
• 3e8ba03 feat(conformance): project which public repos call repo-standard, and how (#383)
• 0ee10a7 chore(burndown): add the kit and archive the 2026-09-03 Desk run (#378)
• af649d8 chore(bootstrap): pin 73805c56b738 and re-record digests (#376)
• 73805c5 verb-server: graph mode refuses a window, and three doc claims stop being fal...
• ed7c381 discoverability: assert the name a client must TYPE, not the one we store (#375)
• 6e32458 Re-roll the org Claude harness baseline (#370)
• 10582a2 pr-claim: when an issue is unreadable, say why and what to do (#369)
• 9d83046 org-repair.sh: canonical bytes, and a digest pin so it cannot drift silently ...
• Additional commits viewable in compare view

Updates step-security/harden-runner from 2.21.0 to 2.21.1

Release notes

Sourced from step-security/harden-runner's releases.

v2.21.1

What's Changed

• Improved performance of the disable-sudo feature.
• Fixed an issue in the Community tier where new endpoints required by the GitHub Actions runner were not being implicitly allowed in block mode.
• Fixed the Harden-Runner post step failing on Linux distributions that do not have a merged /usr filesystem layout (for example Debian 11), where /usr/bin/echo does not exist. This mainly affected self-hosted runners.
• Documentation updates: clarified which features are in the Community (free) vs Enterprise tier.

Full Changelog: step-security/harden-runner@v2.21.0...v2.21.1

Commits

• e14015d Merge pull request #690 from step-security/rc-43
• 9001249 docs: update harden-runner version pin to v2.21.0 in getting started example
• a447fba docs: expand enterprise feature list and document custom VM and ubuntu-slim l...
• b0eaf8d docs: clarify community vs enterprise tiers and add maintained actions section
• 063e8e3 Merge pull request #687 from rohan-stepsecurity/rp/fix/bin-echo-fallback
• f46bdc1 chore: bump agent-ebpf to v1.9.1 and agent to v0.16.3
• 42e6daa fix: fall back to /bin/echo for non-usr-merged distros
• See full diff in compare view

Updates bounded-systems/mint/.github/workflows/release-provenance.yml from 0.5.0 to 0.8.0

Release notes

Sourced from bounded-systems/mint/.github/workflows/release-provenance.yml's releases.

v0.8.0

0.8.0 — 2026-08-23

Minor

• npm-publish.yml — a reusable npm publish lane, and one prescribed release entry point per repo (npm validates the CALLING workflow)

v0.7.2

0.7.2 — 2026-08-22

Patch

• mint release no longer dies with Command failed: git config --get commit.gpgsign on a machine that has not opted into commit signing — an unset key is the default, not an error. And the release tag is annotated with --cleanup=verbatim, so the changelog entry's ## <version> and ### <bump> headings survive into the tag and the GitHub release notes; git's default strips every line beginning with #, which silently reduced the annotation to bullets on every tag mint has ever cut and merged a multi-section entry's Minor and Patch changes into one undifferentiated list.

v0.7.1

• release-cut.yml writes the changelog entry as the tag annotation instead of the tag name, so a CI-cut release gets the same GitHub release notes a laptop cut does. Both release workflows publish with --notes-from-tag, so the annotation is the notes; the text is read out of the release Statement the cut already derives, making it byte-identical to the entry that Statement attests.

v0.7.0

Changelog

Sourced from bounded-systems/mint/.github/workflows/release-provenance.yml's changelog.

0.8.0 — 2026-08-23

Minor

• npm-publish.yml — a reusable npm publish lane, and one prescribed release entry point per repo (npm validates the CALLING workflow)

0.7.2 — 2026-08-22

Patch

• mint release no longer dies with Command failed: git config --get commit.gpgsign on a machine that has not opted into commit signing — an unset key is the default, not an error. And the release tag is annotated with --cleanup=verbatim, so the changelog entry's ## <version> and ### <bump> headings survive into the tag and the GitHub release notes; git's default strips every line beginning with #, which silently reduced the annotation to bullets on every tag mint has ever cut and merged a multi-section entry's Minor and Patch changes into one undifferentiated list.

0.7.1 — 2026-08-22

Patch

• release-cut.yml writes the changelog entry as the tag annotation instead of the tag name, so a CI-cut release gets the same GitHub release notes a laptop cut does. Both release workflows publish with --notes-from-tag, so the annotation is the notes; the text is read out of the release Statement the cut already derives, making it byte-identical to the entry that Statement attests.

0.7.0 — 2026-08-22

Minor

• Relicensed to MIT (org license tiering, #34). The manifests changed in the 0.6.0 bump, but 0.6.0 was manifest-only and was never tagged or published — 0.7.0 is the first release that actually ships under MIT. Everything up to and including 0.5.0 remains under PolyForm-Noncommercial-1.0.0.
• release-provenance.yml takes a tag input, so it can be chained after release-cut.yml. It defaults to the triggering ref, leaving the on: push: tags path every consumer uses today byte-identical; a chained caller passes the cut tag rather than getting the branch.
• mint adopts its own release-cut: a new cut workflow dispatches the tag cut in CI and chains release.yml as a dependent job, so a release no longer needs a laptop. release.yml gains a workflow_call trigger and a tag input; its push: tags trigger is unchanged, so a locally-cut release still works.
• release-provenance: create the GitHub release as a draft and publish it only once assets are attached, so a separate binaries job can no longer hit 422: Cannot upload assets to an immutable release; adds assets-artifact (attach a caller artifact from the same run) and finalize inputs

Commits

• 37d3bb7 release.yml: a recovery door, which mint of all repos needs (#51)
• 1e2b2f9 Version 0.8.0 (#50)
• 66e3b42 npm-publish.yml: own the npm lane, and prescribe one release entry point (#49)
• 44d61e1 Version 0.7.2 (#47)
• 12edc64 Annotate the tag with --cleanup=verbatim, and stop dying on an unset commit.g...
• 854c9f8 Version 0.7.1 (#44)
• 9d062b1 Write the changelog as the tag annotation, not the tag name (#43)
• 01951d9 Version 0.7.0 (#40)
• eca6eb0 Adopt release-cut on mint itself (#41)
• 37c4824 Give release-provenance a tag input, so it composes with release-cut (#38)
• Additional commits viewable in compare view

Updates bounded-systems/.github/.github/workflows/repo-standard.yml from 99e88a0335519cb78be8a1b6623105613fa6aca1 to 2cd9ebc0a2543b3ba11dc7673b351a9d1f6c9445

Commits

• 2cd9ebc _auto-merge: one reusable arming lane, minting through the broker (#387)
• b267ca5 fix(conformance): the publish step passed the snapshot through argv, and argv...
• 3e8ba03 feat(conformance): project which public repos call repo-standard, and how (#383)
• 0ee10a7 chore(burndown): add the kit and archive the 2026-09-03 Desk run (#378)
• af649d8 chore(bootstrap): pin 73805c56b738 and re-record digests (#376)
• 73805c5 verb-server: graph mode refuses a window, and three doc claims stop being fal...
• ed7c381 discoverability: assert the name a client must TYPE, not the one we store (#375)
• 6e32458 Re-roll the org Claude harness baseline (#370)
• 10582a2 pr-claim: when an issue is unreadable, say why and what to do (#369)
• 9d83046 org-repair.sh: canonical bytes, and a digest pin so it cannot drift silently ...
• Additional commits viewable in compare view

Updates bounded-systems/mint/.github/workflows/version.yml from 0.5.0 to 0.8.0

Release notes

Sourced from bounded-systems/mint/.github/workflows/version.yml's releases.

v0.8.0

0.8.0 — 2026-08-23

Minor

• npm-publish.yml — a reusable npm publish lane, and one prescribed release entry point per repo (npm validates the CALLING workflow)

v0.7.2

0.7.2 — 2026-08-22

Patch

• mint release no longer dies with Command failed: git config --get commit.gpgsign on a machine that has not opted into commit signing — an unset key is the default, not an error. And the release tag is annotated with --cleanup=verbatim, so the changelog entry's ## <version> and ### <bump> headings survive into the tag and the GitHub release notes; git's default strips every line beginning with #, which silently reduced the annotation to bullets on every tag mint has ever cut and merged a multi-section entry's Minor and Patch changes into one undifferentiated list.

v0.7.1

• release-cut.yml writes the changelog entry as the tag annotation instead of the tag name, so a CI-cut release gets the same GitHub release notes a laptop cut does. Both release workflows publish with --notes-from-tag, so the annotation is the notes; the text is read out of the release Statement the cut already derives, making it byte-identical to the entry that Statement attests.

v0.7.0

Changelog

Sourced from bounded-systems/mint/.github/workflows/version.yml's changelog.

0.8.0 — 2026-08-23

Minor

• npm-publish.yml — a reusable npm publish lane, and one prescribed release entry point per repo (npm validates the CALLING workflow)

0.7.2 — 2026-08-22

Patch

• mint release no longer dies with Command failed: git config --get commit.gpgsign on a machine that has not opted into commit signing — an unset key is the default, not an error. And the release tag is annotated with --cleanup=verbatim, so the changelog entry's ## <version> and ### <bump> headings survive into the tag and the GitHub release notes; git's default strips every line beginning with #, which silently reduced the annotation to bullets on every tag mint has ever cut and merged a multi-section entry's Minor and Patch changes into one undifferentiated list.

0.7.1 — 2026-08-22

Patch

• release-cut.yml writes the changelog entry as the tag annotation instead of the tag name, so a CI-cut release gets the same GitHub release notes a laptop cut does. Both release workflows publish with --notes-from-tag, so the annotation is the notes; the text is read out of the release Statement the cut already derives, making it byte-identical to the entry that Statement attests.

0.7.0 — 2026-08-22

Minor

• Relicensed to MIT (org license tiering, #34). The manifests changed in the 0.6.0 bump, but 0.6.0 was manifest-only and was never tagged or published — 0.7.0 is the first release that actually ships under MIT. Everything up to and including 0.5.0 remains under PolyForm-Noncommercial-1.0.0.
• release-provenance.yml takes a tag input, so it can be chained after release-cut.yml. It defaults to the triggering ref, leaving the on: push: tags path every consumer uses today byte-identical; a chained caller passes the cut tag rather than getting the branch.
• mint adopts its own release-cut: a new cut workflow dispatches the tag cut in CI and chains release.yml as a dependent job, so a release no longer needs a laptop. release.yml gains a workflow_call trigger and a tag input; its push: tags trigger is unchanged, so a locally-cut release still works.
• release-provenance: create the GitHub release as a draft and publish it only once assets are attached, so a separate binaries job can no longer hit 422: Cannot upload assets to an immutable release; adds assets-artifact (attach a caller artifact from the same run) and finalize inputs

Commits

• 37d3bb7 release.yml: a recovery door, which mint of all repos needs (#51)
• 1e2b2f9 Version 0.8.0 (#50)
• 66e3b42 npm-publish.yml: own the npm lane, and prescribe one release entry point (#49)
• 44d61e1 Version 0.7.2 (#47)
• 12edc64 Annotate the tag with --cleanup=verbatim, and stop dying on an unset commit.g...
• 854c9f8 Version 0.7.1 (#44)
• 9d062b1 Write the changelog as the tag annotation, not the tag name (#43)
• 01951d9 Version 0.7.0 (#40)
• eca6eb0 Adopt release-cut on mint itself (#41)
• 37c4824 Give release-provenance a tag input, so it composes with release-cut (#38)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions