Repository navigation
chore(release): the 1.0 release state — acceptance report, publish path, package metadata - #10
Merged
Merged
Conversation
Three files in the tree cite docs/acceptance-report.md (Gate 3, Gate 8, Gate 10) and the document did not exist. This is that document: every gate with the claim it makes and the test that pins it, the guards that are not numbered gates, which layers have run against a real host and which are offline only, and the limits the report does NOT cover.
…nd RELEASING.md Publishing was an unchecked roadmap box with no path behind it. Now: every publishable package carries license/repository/files/publishConfig (20 packages), a v* tag verifies the tagged tree and keeps the publish job inert until the PUBLISH_ENABLED repository variable is set, and docs/RELEASING.md states the two things that are still human decisions — the CLI cannot ship as `takumi` (taken on npm, 0.8.2 by another publisher), and NPM_TOKEN must exist as a secret. The root package stays private on purpose: half a workspace must not publish.
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.
Finishes what 1.0 was missing on the publishing side.
takumi(taken on npm, 0.8.2 by another publisher), and NPM_TOKEN must exist as a secret.Tested on this tree: 606 tests, 0 failing.