chore: post-first-release cleanup (tag pattern + npm badge)#147
Merged
Conversation
- nx.json: set release.releaseTagPattern to 'v{version}' so future
releases produce tags like 'v0.0.2' (matches the workflow trigger
'tags: v*'). The first release accidentally used Nx's default
fixed-group pattern ('publishable-v0.0.1') so the publish workflow
didn't fire on tag push. From the next release onward, tags use the
conventional 'v{version}' shape and the workflow auto-publishes.
- README.md: fix the stale npm version badge URL (was pointing at the
old @cacheplane/angular package; now points at @ngaf/langgraph).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Two small fixes after shipping 0.0.1:
Release tag pattern. First release accidentally tagged `publishable-v0.0.1` (Nx's default fixed-group pattern). The publish workflow trigger is `tags: v*` so it didn't fire on push. Setting `release.releaseTagPattern: 'v{version}'` means future releases produce `v0.0.2`, `v0.0.3`, etc. — workflow auto-publishes from the next release onward.
README npm badge. The npm version badge URL still pointed at `@cacheplane%2Fangular` (stale before the rename). Fixed to `@ngaf%2Flanggraph` matching the link target.
What this does NOT do
🤖 Generated with Claude Code