Repository navigation
SurfacePin: describe the frozen jcs-v2 format and pin 1.6.1 - #61
Merged
Merged
Conversation
/spec/surfacepin now states the frozen format (canonicalization surfacepin-jcs-v2 in lockfile v3), what is hashed (titles, annotations.title, opt-in instructions), that older jcs-v1 lockfiles still verify and unknown profiles exit 2, and the compatibility promise, with a link to SPEC.md section 0. The FAQ no longer says titles and instructions are not pinned. Install and softwareVersion move to 1.6.1; JSON-LD says Node.js 22+. The site version guard fails until surfacepin 1.6.1 is on npm.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Merged
This branch had an error being 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
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.
Updates /spec/surfacepin for the frozen surfacepin-jcs-v2 format. It adds the compatibility promise section, and the install command and spec links now point at SurfacePin 1.6.1.
Merge right after the npm publish of surfacepin@1.6.1 is approved, not before. 1.6.1 is staged on npm and waiting for 2FA approval. Until it is published, the version guard fails because it checks that the pinned version is on npm. That is the only expected failure.