[Nikhil (shadowfax92)]

Summary

• Bump @browseros/server version 0.0.97 → 0.0.98 so the next release publishes a new versioned artifact to Cloudflare R2 instead of overwriting the already-published 0.0.97.
• Updated apps/server/package.json and bun.lock in lockstep (matching the canonical bump shape of prior commit 2403c0d9).

Design

The release pipeline treats apps/server/package.json#version as the single source of truth: nightly-macos-build.yml reads it and passes it to release-server.yml, which re-reads the same file and fails the build if they disagree. scripts/build/server/{config.ts,archive.ts} read the same field and derive the R2 object keys — artifacts/server/latest/… (always overwritten) and artifacts/server/<version>/…. Bumping the one field is therefore sufficient and complete: a re-run at 0.0.97 would mutate the published 0.0.97/ objects, whereas 0.0.98 creates a fresh versioned key and cleanly repoints latest/.

The "…(e.g. 0.0.97)" strings in release-server.yml are input description doc-text, not functional defaults, so they are intentionally left untouched.

Test plan

• apps/server/package.json and bun.lock both read 0.0.98 (no 0.0.97 remaining)
• bun install --frozen-lockfile → "no changes" (lockfile consistent)
• bun run typecheck → green
• bun test scripts/build/server/stage.test.ts → 11 pass
• Adversarial review (2 rounds) → clean
• Confirm release-gating precondition (CLAUDE.md bundled-VM/WS6) is satisfied before an actual publish

[Nikhil (shadowfax92)]

Greptile (@greptileai) review

[Nikhil (shadowfax92)]

Claude (@claude) review

[claude]

Claude finished Nikhil (@shadowfax92)'s task in 57s —— View job

---

Code Review

• Gather PR context
• Read changed files
• Review diff
• Post review feedback

---

LGTM — this is a clean, minimal version bump with a solid rationale.

What was reviewed

File	Change
packages/browseros-agent/apps/server/package.json	"version": "0.0.97" → "0.0.98"
packages/browseros-agent/bun.lock	corresponding workspace entry updated to match

Findings

No issues. The change is correct and complete:

• The two modified fields are the only two places in the repo that encode this package's version (package.json is the source of truth; bun.lock mirrors it). No other files need updating (the "e.g. 0.0.97" strings in release-server.yml lines 7 and 22 are description: doc-text on workflow_dispatch/workflow_call inputs — not functional defaults — so leaving them as-is is correct).
• The lockfile update is exactly the right shape: only the apps/server workspace entry changes, nothing else drifts.
• The design rationale holds up against release-server.yml: the workflow takes the version as an input and the R2 key derivation (artifacts/server/<version>/…) means bumping here creates a fresh versioned key without touching the already-published 0.0.97/ objects.

One note worth keeping in mind

The test plan has one open checkbox:

Confirm release-gating precondition (CLAUDE.md bundled-VM/WS6) is satisfied before an actual publish

CLAUDE.md explicitly says do not cut a release from dev during the Lima→ContainerRuntime migration window (WS3→WS6). This PR merges the bump, but the actual publish trigger should be held until WS6 lands. That's not a problem with this PR — it's already called out in the test plan — just flagging it as the one gate to verify before pulling the release trigger.

[greptile-apps]

Greptile Summary

Bumps @browseros/server from 0.0.97 to 0.0.98 so the release pipeline publishes a fresh versioned artifact to Cloudflare R2 instead of overwriting the already-published 0.0.97 objects.

• apps/server/package.json: single-field version bump, no other changes.
• bun.lock: matching entry updated to 0.0.98; a grep across the workspace confirms no stale 0.0.97 references remain.

Confidence Score: 5/5

Safe to merge — only two lines change and both are in lockstep.

The entire change is a single version string updated in package.json and the corresponding bun.lock entry. A workspace-wide grep confirms no 0.0.97 references remain, the lockfile is internally consistent, and the PR description explains the release-pipeline contract clearly. There is nothing functional at risk.

No files require special attention.

Important Files Changed

Filename	Overview
packages/browseros-agent/apps/server/package.json	Version field bumped from 0.0.97 to 0.0.98; no other changes.
packages/browseros-agent/bun.lock	Lockfile entry for apps/server updated to match new 0.0.98 version; lockfile is internally consistent.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["nightly-macos-build.yml\nreads version from package.json"] --> B["release-server.yml\nreads & validates version"]
    B --> C{"version matches?"}
    C -- yes --> D["scripts/build/server/config.ts\nderives R2 object keys"]
    C -- no --> E["Build FAILS"]
    D --> F["R2: artifacts/server/latest/…\n(always overwritten)"]
    D --> G["R2: artifacts/server/0.0.98/…\n(new versioned key)"]

Loading

_{Reviews (1): Last reviewed commit: "fix: sync bun.lock to server v0.0.98 (lo..." | Re-trigger Greptile}

[greptile-apps]

Greptile Summary

Bumps @browseros/server from 0.0.97 to 0.0.98 so the next release pipeline run publishes to a fresh versioned R2 key rather than overwriting the already-published 0.0.97 artifact. Both package.json and bun.lock are updated in lockstep and no stale 0.0.97 references remain anywhere in the workspace.

• apps/server/package.json: version field incremented to 0.0.98.
• bun.lock: corresponding workspace entry updated to match, keeping the lockfile consistent.

Confidence Score: 5/5

Safe to merge — the change is a minimal, self-contained version bump with no logic changes.

Both changed files touch only the version string. The lockfile entry is consistent with package.json, no stale 0.0.97 references remain in the workspace, and the pipeline's version-agreement check will enforce correctness at release time.

No files require special attention.

Important Files Changed

Filename	Overview
packages/browseros-agent/apps/server/package.json	Single-line version bump from 0.0.97 to 0.0.98; no other fields changed.
packages/browseros-agent/bun.lock	Lockfile entry for @browseros/server updated from 0.0.97 to 0.0.98, consistent with package.json.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[nightly-macos-build.yml\nreads package.json version] --> B{version == 0.0.98?}
    B -- yes --> C[release-server.yml\nreads package.json again]
    C --> D{versions agree?}
    D -- yes --> E[Build artifacts]
    E --> F[Upload to R2:\nartifacts/server/latest/…]
    E --> G[Upload to R2:\nartifacts/server/0.0.98/…\nnew key – no overwrite]
    D -- no --> H[Build fails]
    B -- no --> H

Loading

_{Reviews (2): Last reviewed commit: "fix: sync bun.lock to server v0.0.98 (lo..." | Re-trigger Greptile}

[github-actions]

✅ Tests passed — 1004/1010

Suite	Passed	Failed	Skipped
✅ agent	96/96	0	0
✅ build	17/17	0	0
✅ eval	95/95	0	0
✅ server-agent	246/246	0	0
✅ server-api	95/95	0	0
✅ server-browser	4/4	0	0
✅ server-integration	10/10	0	0
✅ server-lib	185/186	0	1
✅ server-root	45/48	0	3
✅ server-tools	211/213	0	2

View workflow run