release: prepare Atet 3.1.1 npm bootstrap - #40
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Preserve the 3.1.1 publication contracts while integrating Nebula Sans assets, reviewed package bounds, font notices, and the compiled CLI's native bootstrap closure.
0thernet
changed the title
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.
Summary
@hraness/atet@3.1.1source and package policy for a future first public npm releaseExisting branch-head evidence
The remote head
b160f3a25e7b73b9e438807c7970d71946f2a186previously passed its CI, Required, VTracer, and Vercel checks. Its historical package gate reported 307 files, 2,533,635 packed bytes, 7,354,703 unpacked bytes, and clean Bun/npm consumers.That evidence predates the latest
main. The revived successor is being reconciled with currentmain; its exact-current validation and generated-artifact evidence must replace this section before merge.Publication, trusted-publisher configuration, a version tag, and a GitHub Release remain outside this pull request and require separate authority after a verified main-branch artifact exists.