PDX-0: chore(release) — bump version to 1.5.2-beta.1#189
Merged
Conversation
RCA: Develop accumulated 7 PRs from Sessions 6/7 backlog (PDX-485 thread-prep, PDX-486 VALIDATE-TYPO A+B, PDX-489 G3 DATA-001, PDX-490 G5 error_category, PDX-492 H2a provar_org_describe, PDX-493 H3 valueClass decimal alignment) since 1.5.1 was tagged. Per CLAUDE.md the develop branch tracks <major>.<minor>.<patch>-beta.<n>, so the next publishable version is 1.5.2-beta.1. Without this bump a publish from develop would clash with 1.5.1 on the registry. Fix: Bump package.json.version, server.json.version (top-level), and server.json.packages[0].version from 1.5.1 to 1.5.2-beta.1, keeping all three identical per the version-sync rule in CLAUDE.md. No source or test changes. yarn compile clean, yarn lint clean, full mocha 1245 passing / 0 failing.
Quality Orchestrator🟢 LOW · No test files mapped. ⚡ quality-orchestrator · |
Contributor
There was a problem hiding this comment.
Pull request overview
Bumps the CLI/MCP server version to 1.5.2-beta.1 to align develop’s pre-release versioning with the repo’s <major>.<minor>.<patch>-beta.<n> convention and avoid clashing with the last tagged release (1.5.1).
Changes:
- Updated
package.jsonpackage version to1.5.2-beta.1. - Updated
server.jsontop-levelversionandpackages[0].versionto1.5.2-beta.1to keep version fields in sync.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| server.json | Bumps MCP server/version metadata (top-level and package entry) to 1.5.2-beta.1. |
| package.json | Bumps npm package version to 1.5.2-beta.1. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
13 tasks
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
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.
Context
Develop is ahead of 1.5.1 (the last tagged release) by 13 commits spanning 7 PRs from the Sessions 6/7 backlog:
warningCodes.tsenumerror_category+retryableon test-run failuresprovar_org_describetool reading Provar workspace.metadatacachevalueClassdispatch (canonical-reference alignment)Per
CLAUDE.md, the develop branch tracks<major>.<minor>.<patch>-beta.<n>. Bumping to1.5.2-beta.1so the next publish from develop doesn't clash with the released1.5.1.Files changed
package.json—version: "1.5.1"→"1.5.2-beta.1"server.json— top-levelversionANDpackages[0].versionupdated in lock-step per the version-sync ruleVerification
yarn compile— cleanyarn lint— clean (incl.lint:script-names)node_modules/.bin/mocha "test/**/*.test.ts"— 1245 passing / 1 pending / 0 failinggit diff)Next step
After this merges to develop, open the release PR develop → main and tag
v1.5.2on the release merge commit.