Repository navigation
release: qualify Scanly v2.1.0 artifacts and first-publish provenance - #58
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Release-qualified 2.1.0 candidate. Product source remains 6b017b5 (tree c72430a2ab0a2d47e7cd095325088f1e053a5c41). Eleven npm tarballs were built independently on two GitHub-hosted jobs and match byte-for-byte; 22 detached provenance bundles passed issuer, identity and exact subject verification. Two exact-source Native workflow runs passed and produced matching AAR contents. Final metadata A/B and selected canonical outputs match across 42 files. SSH signing was actually exercised and verified; the temporary probe tag was deleted. The production deployment is READY on the qualified product source. Existing ten npm OIDC grants were tested through actual token exchange without publishing or persisting credentials. A version/package-scoped, interactive-2FA first-publish plan for @scanly/url-safety preserves its CI provenance; dependencies publish first. npm run stable:manifest:verify -- --require-go passes. New release tools have passing tests and mandatory CI. This PR adds only new v2.1.0 records; v2.0.0/v2.0.1 and Issue #13 remain unchanged. Actual tag/publication/post-publication verification happen after main promotion, not in this PR.