Repository navigation
release: Scanly SDK v2.1.0 — Link Intelligence - #59
Merged
Merged
Conversation
…v2.1 feat: Scanly v2.1.0 Link Intelligence
…cation release: qualify Scanly v2.1.0 artifacts and first-publish provenance
|
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.
Promote the qualified 2.1.0 minor release from develop. The new versioned Stable manifest binds the exact product source, software/security/API evidence, two independent npm builds, verified detached provenance, two Native builds, final metadata reproducibility, signing proof and READY production deployment. Existing npm packages retain their verified OIDC publication path; only the new @scanly/url-safety package uses the explicitly qualified interactive first-publication bootstrap with CI provenance, after its dependencies exist. No placeholder version, credential in CI, or provenance waiver. v2.0.0/v2.0.1 records and Issue #13 remain immutable/independent. The signed tag and publications are not yet created; Stable Release Gate must pass before promotion.