-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove timestamp from checkpoint #1888
Remove timestamp from checkpoint #1888
Conversation
Fixes sigstore#1887. Verified that checkpoints are still verifiable with and without timestamps (since timestamps are just a part of the existing OtherContent, this is not a breaking change). Looking over all of the Sigstore org, no project is relying on the timestamp. Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1888 +/- ##
==========================================
- Coverage 66.46% 66.40% -0.06%
==========================================
Files 92 92
Lines 9213 9194 -19
==========================================
- Hits 6123 6105 -18
+ Misses 2346 2345 -1
Partials 744 744
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
This seems to break node LTS 20 which comes with an older npm which does not have a change to account for this change. So it is breaking. See: |
Fixes #1887. Verified that checkpoints are still verifiable with and without timestamps (since timestamps are just a part of the existing OtherContent, this is not a breaking change).
Looking over all of the Sigstore org, no project is relying on the timestamp.
Summary
Release Note
Documentation