chore(openspec): archive add-ci-and-npm-publish-automation - #39
Merged
Conversation
Automatic sync succeeded — 14 requirements written into two new main specs, no manual delta application needed. openspec validate --specs: 50/50. - continuous-integration: 9 requirements, 22 scenarios - npm-package-cicd: 5 requirements, 14 scenarios Task 6.8 (end-to-end publish verification) was removed rather than left unchecked. Reaching the OIDC authentication step requires an actual npm publish, and neither package's src/ had changed since its last release, so under this change's own rules neither was due for one — publishing an identical tarball under a new number purely to exercise the pipeline is not a trade worth making against a registry that cannot be un-published. design.md records what is verified (version comparison, check job on a real runner, job-to-job outputs, the skip path running for real on master) and what is not, plus why finding out late is cheap: a failed publish leaves the registry untouched, and the tag is created only after a successful one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PgfFLCcVjPxZJmMspbY4Bu
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.
Archives the change behind #36. The CLI's automatic sync succeeded — no manual delta application needed, and
openspec validate --specspasses 50/50 (up from 48).Two new capabilities, both purely additive:
continuous-integrationnpm-package-cicdTask 6.8 removed rather than left unchecked. Reaching the OIDC authentication step needs a real
npm publish, and neither package'ssrc/had changed since its last release — so under this change's own rules neither was due for one, and publishing an identical tarball under a new number just to exercise the pipeline is a bad trade against a registry that cannot be un-published.design.mdnow carries both a Verified at implementation time section and a Knowingly unverified one. What ran for real: the version comparison against the live registry, the check job on a real runner, job-to-job output passing, and the skip path (exercised when #36 merged — both packages skipped, nothing published, run green). What has never executed:npm publishitself. Finding out late is cheap — a failed publish leaves the registry untouched, and the tag is created only after a successful one.Touches
openspec/only.