[codex] Attest release artifacts - #30
Merged
Merged
Conversation
ygsgdbd
marked this pull request as ready for review
July 24, 2026 04:33
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
User impact
Homebrew installs can launch directly through the custom cask behavior, while the README remains explicit that TypeSwitch is unsigned and not notarized. Release downloads also gain GitHub build provenance that users can verify with
gh attestation verify.Validation
rtk just checkpassedactionlintpassed after ignoring two existing unrelated findings:SC2129in checksum generation and the existingsoftprops/action-gh-release@v1git diff --checkpassed