Implement build provenance attestations before release creation#115
Merged
Implement build provenance attestations before release creation#115
Conversation
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add support for immutable releases
Implement immutable releases with build provenance attestations
Feb 27, 2026
There was a problem hiding this comment.
Pull request overview
This pull request implements GitHub's Immutable Releases feature with build provenance attestations to enhance supply chain security for DedPaste releases. The changes add cryptographic attestation generation to the release workflow and provide comprehensive documentation for users to verify release authenticity.
Changes:
- Added
attestations: writepermission and build provenance attestation steps usingactions/attest-build-provenance@v2to the release workflow - Updated release notes generation to include verification instructions for attestations
- Added verification section to README.md with examples of using
gh attestation verify - Created comprehensive RELEASE-PROCESS.md documentation covering the full release process, attestation verification, and troubleshooting
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
.github/workflows/release-with-sbom.yml |
Added attestation permissions and attestation steps for SBOM and build artifacts; updated release notes to include verification instructions |
README.md |
Added verification section demonstrating how to verify release artifacts using GitHub CLI attestation commands |
docs/RELEASE-PROCESS.md |
New comprehensive documentation explaining the release process, immutable releases feature, attestation implementation, verification steps, and troubleshooting guidance |
… immutability settings Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Copilot
AI
changed the title
Implement immutable releases with build provenance attestations
Reflect active immutability in release documentation
Feb 28, 2026
Copilot
AI
changed the title
Reflect active immutability in release documentation
Implement build provenance attestations before release creation
Feb 28, 2026
github-actions bot
added a commit
that referenced
this pull request
Feb 28, 2026
Version bump type: patch PR: #115 Title: Implement build provenance attestations before release creation
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.
Build provenance attestations must be created before publishing releases to ensure proper artifact association at publication time.
Changes
Create GitHub Release(line 519)Implementation
Attestations are cryptographically signed and verifiable via
gh attestation verify.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.