Release version 0.1.1 and token-optional npm publication - #72
Merged
Merged
Conversation
Bump every enforced version touchpoint to 0.1.1: the root and three adapter packages, the Helm appVersion and image tag, the MCP server version, the Claude channel protocol version, and the forward-facing site references. The v0.1.0 tag never produced a release: all four workflow runs failed publishing the first @plannotator adapter to npm, so no GitHub release, image, or packages exist for it. The release workflow now skips npm publication with a notice when NPM_TOKEN is not configured instead of failing the run, so the GitHub release and image publication proceed. The adapters are published locally by the maintainer until npm trusted publishing is set up. Claude-Session: https://claude.ai/code/session_01EcbEctwH1oDTrYhqHe6n9g
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.
Prepares the first release that will actually ship. The v0.1.0 tag never produced a release: all four workflow runs (Aug 28–Sep 3) failed at "Publish public npm adapters" with an npm E404 (the token could not create new packages in the @plannotator scope), and "Create GitHub release" is gated behind it — so no GitHub release, GHCR image, or npm packages exist, while docs claim otherwise.
appVersionand image tag, MCPserverVersion, Claude channelchannelVersion, plus the site's forward-facing v0.1.0 references (get-started, deploy, security, docs index).NPM_TOKENis not configured instead of failing, so the GitHub release and image publication can complete. Adapters will be published locally by the maintainer (security-key auth); npm trusted publishing can replace this later.Verified:
check:release-version --tag v0.1.1andverify:sitepass locally. After merge: annotated tagv0.1.1on main triggers the release run.https://claude.ai/code/session_01EcbEctwH1oDTrYhqHe6n9g