Skip to content

chore(release): bump version pins 0.8.3 -> 0.9.0 (#278) - #279

Merged
simpros merged 1 commit into
mainfrom
gh-278-release-prep-v0-9-0-bump-version
Oct 5, 2026
Merged

simpros merged 1 commit into
mainfrom
gh-278-release-prep-v0-9-0-bump-version

Conversation

@simpros

@simpros simpros commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Closes #278

Why the change

Issue #278 is implemented on gh-278-release-prep-v0-9-0-bump-version but the work was never shipped, so this closes it out.

Special things to note

  • Recovered unmodified: the branch is pushed as the agent left it, with no review round yet.

Change outline

The commit(s) closed out on gh-278-release-prep-v0-9-0-bump-version:

ba32f84 chore(release): bump version pins 0.8.3 -> 0.9.0
 .github/workflows/preview.yml                       |  6 +++---
 Dockerfile                                          |  2 +-
 apps/cli/package.json                               |  2 +-
 apps/server/package.json                            |  2 +-
 bun.lock                                            |  6 +++---
 deploy/coolify/README.md                            |  2 +-
 deploy/coolify/gateway.compose.yml                  |  2 +-
 docs/ci-integration.md                              | 10 +++++-----
 docs/getting-started.md                             |  4 ++--
 docs/operator-deploy.md                             |  8 ++++----
 docs/telemetry.md                                   |  6 +++---
 examples/adopting-repo/.github/workflows/sprout.yml |  4 ++--
 examples/adopting-repo/.gitlab-ci.yml               |  2 +-
 package.json                                        |  2 +-
 packages/api-client/package.json                    |  2 +-
 templates/README.md                                 |  6 +++---
 16 files changed, 33 insertions(+), 33 deletions(-)

Every adopter-facing pin names the release about to exist, so an
adopter copying a snippet from main wires up v0.9.0. No adopter
wiring change: .sprout.yaml schema untouched. No tag created here.

Closes #278.
@simpros

simpros commented Oct 5, 2026

Copy link
Copy Markdown
Owner Author

🧊 Thermo-nuclear review (round 1) — APPROVE · ba32f84c

  • Residual risks
  • Unverifiable from here
Full report (click to expand)

VERDICT: APPROVE

This is a mechanical release-version bump (0.8.3 → 0.9.0) across 16 files. I verified HEAD == ba32f84ce96d14801845daeff864a8c870c4fb01 and reviewed the complete origin/main...HEAD diff. No source logic changed. The change is consistent and complete for the canonical version carriers.

Consistency verified:

  • All four package.json workspace versions bumped in lockstep: root, apps/cli, apps/server, packages/api-client, plus the three matching bun.lock workspace entries. No drift between them.
  • Dockerfile ARG SPROUT_VERSION default bumped; release workflow still overrides it from the pushed tag (release.yml:93), so the default is only a fallback.
  • Deploy pin (deploy/coolify/gateway.compose.yml) and its README, the reusable workflow example/description (.github/workflows/preview.yml), the adopting-repo examples, and all Docs/Templates references bumped together.
  • Version is never hardcoded in source: sproutVersion() (apps/server/src/telemetry/payload.ts:118) reads the root package.json, and payload.test.ts:23 asserts there is no literal. So the telemetry payload/docs (docs/telemetry.md) track automatically and the doc examples match reality.
  • grep for 0.8.3 across the tree (excluding node_modules/.git) returns 0 hits; no stale pin was left behind. No conflict markers, no whitespace noise.

No structural findings. No file-size concerns (edits are one-liners). No new branching, abstraction, cast, or boundary churn — nothing to judge against the design rubric. Behavior is unchanged apart from the reported version string, which is the intent.

Minor, non-blocking observation (pre-existing, not a regression introduced here): the release-prep sweeps example annotations like (e.g. v0.8.3) → (e.g. v0.9.0) in some files, but two example strings remain at older versions — templates/preview.yml:4 (e.g. v0.6.0) and .github/workflows/release.yml:10 (e.g. v0.2.0). They were already stale before this MR, so I would not block on them; if the team wants the sweep exhaustive, fold them in. Similarly, docs phrases such as "Replace ... v0.9.0 with the adopted release" are now somewhat circular, but that phrasing pattern predates this bump.

Residual risks

  • v0.9.0 tag/image not yet published while docs now point users at it: probe gh release view v0.9.0 and docker manifest inspect ghcr.io/simpros/sprout:0.9.0; both must resolve before merge-to-main docs go live.
  • Remote-include docs now fetch raw.githubusercontent.com/simpros/sprout/v0.9.0/templates/preview.yml: probe with curl -fsI https://raw.githubusercontent.com/simpros/sprout/v0.9.0/templates/preview.yml.
  • Coolify compose pins ghcr.io/simpros/sprout:0.9.0; probe docker pull ghcr.io/simpros/sprout:0.9.0 before operators copy the stack.
  • Telemetry install id/version reporting: probe a boot and check the emitted sprout_version field is 0.9.0 (it derives from root package.json, so this should hold).

Unverifiable from here

Whether the v0.9.0 git tag and GHCR image are actually published, and whether any external consumer (GitLab component repo, Coolify resource copies) has been updated out of band.

REPORT READY review-report.md


Automated agent review (opencode) · worktree /home/sim/.herdr/worktrees/sprout/gh-278-release-prep-v0-9-0-bump-version · subsequent rounds will reply in this thread.

@simpros
simpros merged commit 396f392 into main Oct 5, 2026
2 checks passed
@simpros
simpros deleted the gh-278-release-prep-v0-9-0-bump-version branch October 5, 2026 11:39
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.

Release prep v0.9.0: bump version pins

1 participant