Skip to content

chore: complete mint adoption — release provenance + re-pin v0.3.1 - #5

Merged
bdelanghe merged 2 commits into
mainfrom
adopt-mint-v0.3.1
Jun 29, 2026
Merged

chore: complete mint adoption — release provenance + re-pin v0.3.1#5
bdelanghe merged 2 commits into
mainfrom
adopt-mint-v0.3.1

Conversation

@bdelanghe

Copy link
Copy Markdown
Contributor

Complete this repo's mint adoption. It already runs the version caller but was pinned to mint v0.2.0 (440c191) and never gained the release-provenance caller.

This PR:

  1. Re-pins version.yml to mint v0.3.1 (validates .release/ intents + previews the next bump on every PR).
  2. Adds release.yml — mint's reusable release-provenance.yml: on a v* tag (cut by mint release) it emits + keyless-signs the in-toto release Statement (tag → version plan → commit) and attaches it to the GitHub release.

The existing registry publish workflow is untouched — mint owns version + tag + provenance; the registry push stays where it is.

Mirrors the reference adoption bounded-systems/conformance-kit#30.

Draft — part of the org-wide mint v0.3.1 rollout. Do not merge in isolation; see recommended batch order.

🤖 Generated with Claude Code

bdelanghe and others added 2 commits June 29, 2026 02:28
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@bdelanghe
bdelanghe marked this pull request as ready for review June 29, 2026 06:35
@bdelanghe
bdelanghe merged commit d5cb7fc into main Jun 29, 2026
5 checks passed
@bdelanghe
bdelanghe deleted the adopt-mint-v0.3.1 branch June 29, 2026 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant