Skip to content

SurfacePin: describe the frozen jcs-v2 format and pin 1.6.1 - #61

Merged
yellowgram merged 1 commit into
masterfrom
surfacepin-spec-1.6.1
Oct 20, 2026
Merged

yellowgram merged 1 commit into
masterfrom
surfacepin-spec-1.6.1

Conversation

@yellowgram

Copy link
Copy Markdown
Owner

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.

/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.
@vercel

vercel Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
yellowgram Error Error Oct 20, 2026 5:04pm UTC

@yellowgram
yellowgram merged commit 05818d9 into master Oct 20, 2026
1 of 2 checks passed

This branch had an error being deployed

1 failed deployment
Preview — da0c8d1b Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant