docs(v1.4): prep conceptual-doc banners + overview history for server v1.4#78
Merged
Conversation
… v1.4 - overview.md: banner 1.3.x → 1.4.x, add v1.4 history entry (tenant scoping, admin ops surface, bootstrap resilience, non-breaking) - repo-map.md: banner 1.3.x → 1.4.x, test-counts label → v1.4.0 - v1-contract.md: banner 1.3.x → 1.4.x - conventions.md: banner 1.3.x → 1.4.x Prepares the surfaces that the server's release-time verify-workspace-versions gate checks against the incoming v1.4.0 tag. SDK rows stay at their independent v1.2.0 pending each SDK's own release.
This was referenced Jul 13, 2026
smaramwbc
added a commit
to smaramwbc/statewave
that referenced
this pull request
Jul 13, 2026
- pyproject.toml: 1.3.0 → 1.4.0 - README.md status blurb + active-development line to v1.4.0 Companion statewave-docs updates (banners → 1.4.x, overview.md v1.4 history entry, test-counts label → v1.4.0, product.md status line → 1.4.0) are landed via smaramwbc/statewave-docs#78 and #79. Release workflow's verify-workspace-versions gate is green against 1.4.0 as truth.
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
Prep-work for the incoming server v1.4.0 tag push, which will trigger
verify-workspace-versionsinsmaramwbc/statewave/.github/workflows/release.yml. That gate checks: banners on the four conceptual docs (overview / repo-map / v1-contract / conventions) matchX.Y.xof truth, the repo-map test-counts label matches truth, andoverview.mdversion-history has a### vX.Yheading.### v1.4 — Tenant scoping & operator resiliencehistory entry (4 bullets: tenant-scoped lookups, admin ops surface, bootstrap resilience, non-breaking additions)(as of v1.3.0) → (as of v1.4.0)SDK rows in repo-map stay at v1.2.0 (they're
independent, per_targets.py) — will bump when each SDK actually ships v1.4.0.Test plan
python tools/check-versions.pylocally against a bumped statewave/pyproject.toml (1.4.0) — dry-runs greenpython tools/check-proof-figures.py— passes (mirrors match SSoT unchanged)v1.4.0tag in smaramwbc/statewave so the release workflow'sverify-workspace-versionsgate finds the aligned surfaces on statewave-docs/main