chore: use actions/attest instead of the wrapper action - #850
Merged
Conversation
actions/attest-build-provenance is only a wrapper on actions/attest as of v4, and new code should use actions/attest. Assisted-by: ClaudeCode:claude-opus-5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 AI text below 🤖
actions/attest-build-provenanceis only a wrapper onactions/attestas of v4, and the upstream docs tell new code to useactions/attest. This replaces every mention: the repo workflow (SHA-pinned to v4.2.2), both cookiecuttercd.ymltemplates, and the GHA guides.Inputs are unchanged:
actions/attestwith onlysubject-pathgenerates SLSA build provenance, like the wrapper did. Permissions are unchanged too; the newartifact-metadata: writepermission is only needed withpush-to-registry.📚 Documentation preview 📚: https://scientific-python-cookie--850.org.readthedocs.build/