Skip to content

docs: v1.0 post-release audit + decision items#235

Open
smaramwbc wants to merge 3 commits into
mainfrom
docs/v1.0-audit
Open

docs: v1.0 post-release audit + decision items#235
smaramwbc wants to merge 3 commits into
mainfrom
docs/v1.0-audit

Conversation

@smaramwbc

Copy link
Copy Markdown
Owner

Post-v1.0 release audit + decision items

Two coherent commits per repo:

  1. Audit pass — removes stale pre-v1.0 language now that v1.0.0 shipped (2026-06-09): version pins → 1.0.0, experimental/MVP/planned/preview maturity labels on shipped features → present tense (real limitations preserved), broken anchors, stale connector versions, missing v1.0 endpoints/params, internal-ops notes removed from public files.
  2. Decision items (where applicable to this repo):
    • Proof figures recomputed from source and reconciled across SSoT + all mirrors (server 876→944 / 660→708 unit; connectors 606→800; py 80; ts 50). check-proof-figures green.
    • /launch → permanent newsletter page: email-only (minimal data), no countdown/launch-date, newsletter consent; server name-required check removed; Footer/Terms/Privacy/Press/llms updated; existing-subscriber consent preserved; +component & backend tests.
    • Helm: server appVersion 0.7.0→1.0.0 (chart 0.2.0); connectors-runner default tag → latest. helm lint/template pass.
    • Package metadata: Development Status :: 5 - Production/Stable + central Issues tracker (py/server/ts). Source-only — registry pages refresh on next release.
    • NOTICE genericized (founder name → Statewave).
    • Replica-routing/cross-region wording made neutral and non-committal.
    • ADMIN_DEMO_WEBHOOK_URL relabeled as self-healing-eval-only (not removed).

Validation: check-versions ✅ · check-proof-figures ✅ · markdownlint 0 errors · web build ✅ + 301 tests ✅ · helm lint ✅ · typecheck ✅.

No version bumps to package manifests, no package/chart publishes, no tags, no deploys. Not for merge yet — review.

Sweep across all public surfaces after the 2026-06-09 v1.0.0 release:
version pins to 1.0.0, stale maturity labels (experimental/MVP/preview/
planned) on shipped features corrected to present tense, broken README
anchors fixed, stale connector versions (v0.18->v0.22) and SDK method
coverage updated, missing v1.0 endpoints/params added to references,
owner-facing/internal-ops notes removed from public files. Proof figures,
helm appVersion, package-manifest metadata, and the /launch page cluster
are intentionally untouched (tracked as decisions). Gates green;
markdownlint 0 errors.
- Proof figures recomputed from source and reconciled across SSoT + all
  mirrors (server 876->944, 660->708 unit; connectors 606->800; py 80; ts 50);
  check-proof-figures gate green.
- /launch converted to a permanent newsletter/updates page: email-only form
  (minimal data), no countdown/launch-date, newsletter consent wording,
  existing-subscriber consent preserved; server name-required check removed;
  Footer/Terms/Privacy/Press/llms updated; +component & backend tests.
- Helm: server appVersion 0.7.0->1.0.0 (chart 0.2.0); connectors-runner
  default image tag -> latest (runner image has no semver tags).
- Package metadata: Development Status 5 - Production/Stable + central Issues
  tracker (py + server + ts); server classifiers/urls added.
- NOTICE genericized (founder name -> Statewave).
- Replica-routing/cross-region wording made neutral and non-committal.
- ADMIN_DEMO_WEBHOOK_URL relabeled as self-healing-eval only (not removed).

No version bumps, no package/chart publishes, no tags.
…nt Status -> Beta

Addresses two post-audit credibility concerns:

- Helm connectors-runner: image tag latest -> sha-44c57b5, the immutable
  per-commit tag byte-identical to the current latest (digest sha256:ef8f5b08...,
  built from connectors commit 44c57b5, runner package 0.3.0). Deploys are now
  reproducible instead of tracking a moving latest. Maintainer note + the exact
  semver follow-up are documented in values.yaml. No image published/retagged.

- pyproject Development Status: 5 - Production/Stable -> 4 - Beta for the server
  (statewave) and the Python SDK (statewave-py). v1.0.0 is the first stable
  release (cut 2026-06-09) with no post-1.0 compatibility track record; Beta is
  the conservative, credible trove signal. The canonical "first stable public
  developer release" prose is unchanged. TS SDK uses no trove classifier and its
  README wording is already conservative (no production-ready/enterprise claims).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant