chore: align workspace version to v0.9.0#14
Merged
Merged
Conversation
v0.9.0 is the TypeScript SDK's independent breaking release (camelCase rename, statewave-ts#103). The server, API contract, and Python SDK have no functional changes since v0.8.0. This bump only realigns the single cross-repo version so the release-time check-versions gate passes. The lockstep-versioning model that forces this is tracked for redesign (decouple per-package versions, coordinate on the API contract instead).
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.
What
Aligns the single cross-repo workspace version to v0.9.0.
v0.9.0is the TypeScript SDK's independent pre-1.0 breaking release (camelCase rename, statewave-ts#103). The server, API contract, and Python SDK have no functional changes since v0.8.0 — this PR only realigns version strings so the release-timecheck-versions.pygate passes. No release tag is pushed by this PR, so nothing is republished.Why this is a band-aid
The lockstep "one version across all repos" model is what forced this. Independent per-package releases will keep re-triggering the same drift. The proper fix — decouple per-package versions, coordinate on the API contract instead — is tracked as a follow-up issue.