Repository navigation
chore(design): track recoverable Penpot snapshots - #545
Merged
Merged
Conversation
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.
Native Penpot exports need a recoverable version record. Add snapshot manifests with per-file revisions and content hashes, a dependency-free integrity checker, and recovery instructions. The publication record explicitly states that native archives remain local and their proposed GitHub release upload awaits approval.
Validation on
cdec52f704502851f69ac54992dbe10df813d31c:The proposed native-archive upload is pending and no downloaded-copy or new native-restore verification is claimed.
Closes #544