Repository navigation
README security summary, and the security page on versioned releases - #11
Merged
Merged
Conversation
kalfasyan
changed the title
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.
Requested by Yannis · project thread
security.mdnow covers the release PRs in the app repos:latestmoves only on a release,edgefollowsmain, every image is attested (with agh attestation verifyexample), and pinning uses release tags. It also says plainly what an attestation does and doesn't prove. The "versioned releases" item is gone from "Not done yet".Merge this after the app release PRs (plasto#32, flowy#23, troye#36, splitwiz#25, should-we#19), and once the first releases are out, so the page never claims more than is true.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KyLYnK7sL7yCwRLtnMhpJP