chore(release): prep @domscribe/protocol@1.0.0 publish artifacts (#39)#40
Closed
Narrator wants to merge 1 commit into
Closed
chore(release): prep @domscribe/protocol@1.0.0 publish artifacts (#39)#40Narrator wants to merge 1 commit into
Narrator wants to merge 1 commit into
Conversation
Authors the release-prep artifacts that issue #39 requires before the gated npm publish: the Kaushik-signoff release-post draft, the operator publish runbook, the seed CHANGELOG entry for the protocol package, and the docs/rcp/v1.md version-banner links that resolve once the tag exists. This PR does NOT execute the publish — that step is gated on Kaushik signoff and on issues #32, #33, #34, #38 landing in main (see runbook §0). The runbook documents the manual operator procedure end-to-end including the non-author verification install, the telemetry smoke, and rollback. Refs: docs/rfcs/0001 (ratified by #36), docs/rfcs/0002 (this sprint's execution doc), docs/sprints/2491.md. Closes: not yet — issue #39 closes only after the publish step in the runbook succeeds and the release post lands. This PR is the prep PR.
|
View your CI Pipeline Execution ↗ for commit b74c45d
☁️ Nx Cloud last updated this comment at |
Member
Author
|
Closing agent-generated PR during workspace cleanup. |
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
Authors the release-prep artifacts that issue #39 requires before the gated
npm publishof@domscribe/protocol@1.0.0:docs/release/v1.0.0-protocol-release-post.md— LinkedIn + X + blog post draft with the 'complement at a different layer' framing per DOP risk note; checkbox-driven Kaushik signoff review.docs/release/v1.0.0-protocol-publish-runbook.md— operator runbook with the prereq table, two publish paths (independent vs. unified versioning), non-author verification install, telemetry smoke, and a rollback section.docs/release/v1.0.0-protocol-changelog.md— seed CHANGELOG entry; operator relocates topackages/protocol/CHANGELOG.mdon the publish branch once [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32 has landed.docs/rcp/v1.md— version-banner and §8 reference link to the forthcoming npm package page andprotocol-v1.0.0release tag (links 404 until the publish step runs; that's expected per runbook §2).What this PR is NOT
npm publishruns. Noprotocol-v1.0.0tag is pushed. Those are runbook steps 5–7, gated on Kaushik signoff AND on [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32 + Normalize MCP tool names — single grammar + alias policy #33 + Opt-in telemetry hook in relay daemon — weekly-active session count #34 + Make SourcePosition required on every resolve_*/query_* output schema #38 being merged intomainfirst.packages/protocol/. The package doesn't exist onmainyet (it lands via [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32). Filing the CHANGELOG underdocs/release/avoids a merge conflict with [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32 and is explicitly handled in runbook §3.Acceptance criteria mapping
@domscribe/protocol@1.0.0resolvable on npmprotocol-v1.0.0; CHANGELOG updated; v1.md banner links to tagRisks & flags
projectsRelationship: \"independent\"for the protocol package. The runbook documents both Path A (preferred, independent) and Path B (fallback, manual publish) so the operator is not blocked if [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32 ships unified versioning. If [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32's author decides this, please flag in [Deferred to RFC 0003-follow-on] Extract @domscribe/protocol package (RCP versioning unit) #32 — issue Publish @domscribe/mcp@1.0.0 (public) + tag RCP v1.0 against @domscribe/core schemas #39's publish path picks accordingly.Test plan
npx prettier --checkon all four changed files — green.docs/rcp/v1.mdbanner links structurally correct (point to canonical npm + GitHub release URLs).References
docs/rcp/v1.md(PR docs(rcp): publish v1.0.0 spec with explicit stability policy #36, on main)docs/rfcs/0001-rcp-as-versioning-unit.md,docs/rfcs/0002-protocol-v1-execution.mddocs/sprints/2491.md