chore: sync package.json versions to 0.32.0 to match npm#145
Merged
willwashburn merged 1 commit intomainfrom Apr 27, 2026
Merged
chore: sync package.json versions to 0.32.0 to match npm#145willwashburn merged 1 commit intomainfrom
willwashburn merged 1 commit intomainfrom
Conversation
A prior publish run for 0.32.0 succeeded on npm for reader/ledger/analyze but failed before the version-bump commit + tags landed; mcp/cli never published. The publish workflow's "local vs npm" parity check now blocks on reader/ledger/analyze (main=0.31.0 < npm=0.32.0). Bump all five packages to 0.32.0 in package.json so the next "all → minor" workflow run cleanly takes everything to 0.33.0 with monorepo parity preserved. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
publish allworkflow run shipped@relayburn/reader@0.32.0,@relayburn/ledger@0.32.0, and@relayburn/analyze@0.32.0to npm but failed before the version-bump commit + git tags landed.@relayburn/mcpand@relayburn/clinever published..github/workflows/publish.yml:120) now blocks becausemainis at 0.31.0 for those three packages while npm has 0.32.0.package.jsonso the nextpublish all → minorrun cleanly takes everything to 0.33.0 with monorepo parity preserved. mcp/cli are bumped along with the others (even though they are not yet on npm at 0.32.0) so a single coordinated bump keeps the five-package release in lockstep.No code changes — only the
versionfield in eachpackages/*/package.json.Follow-ups (not in this PR)
reader-v0.32.0,ledger-v0.32.0,analyze-v0.32.0so the changelog generator has a baseline for the otherwise-untracked 0.32.0 publish.package=all,version=minorto produce 0.33.0.Test plan
mainpackage=all,version=minor🤖 Generated with Claude Code