chore(release): cut 0.2.0 with the deployment routes and the write wrapper - #74
Merged
Conversation
…apper
Deployment and the write path. 0.1.1 could be installed but not really
deployed: there was no guidance on where the control plane should run,
and job.write worked only on jobs the worker itself created, which on a
real estate is almost none of them.
Minor rather than patch — two feat commits, a 45-line addition to the
wire protocol, and migration 0004.
Two things in the changelog need a decision from an upgrader rather than
just a pull, so they are called out under their own heading rather than
left to be discovered:
- RSAGENT_TRUSTED_PROXY_HOPS defaults to 0, which ignores
X-Forwarded-For. Anyone running a proxy has to set it or every audit
row records the proxy rather than the client. Safe unset, just less
precise.
- Migration 0004 runs on first start. One nullable column, so no
rewrite and no maintenance window.
Verified at 0.2.0: typecheck 7/7, lint, proto:check, 363 unit, 18
integration, 25 e2e, audit clean at high. The release workflow's own
version gate was replicated locally — six manifests and WORKER_VERSION
all read 0.2.0, prerelease resolves false, so latest will move on both
registries.
Worth recording because it cost a scare: the standalone bundle check
initially reported 0.1.0. dist/rsagent-worker.mjs was a stale local
artifact — build:sea emits the .cjs and the executable and does not
rewrite the .mjs, so it had survived from an earlier build. Rebuilt from
an empty dist, both the bundle and the executable report 0.2.0. CI
builds from a fresh checkout, so it could not have shipped, but the
local check is worthless without the clean first.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AyYg2j8FVkLjiaVcj5HCkj
semics-tech
changed the title
semics-tech
force-pushed
the
chore/release-0.2.0
branch
from
July 31, 2026 14:58
e369dc2 to
a9b0294
Compare
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.
Deployment and the write path.
0.1.1could be installed but not really deployed — there was no guidance on where the control plane should run, andjob.writeworked only on jobs the worker itself created, which on a real estate is almost none of them.Minor rather than patch: two
featcommits, a 45-line addition to the wire protocol, and migration0004.What an upgrader has to decide
Both are called out under their own heading in the changelog rather than left to be discovered:
RSAGENT_TRUSTED_PROXY_HOPSdefaults to0, which ignoresX-Forwarded-For. Anyone running a proxy in front of the dashboard has to set it, or every audit row and rate-limit bucket records the proxy's address instead of the client's. Safe unset, just less precise.0004runs automatically on first start. One nullable column — no rewrite, no maintenance window.Verified at 0.2.0
typecheck7/7 ·lint·proto:check· 363 unit · 18 integration · 25 e2e ·pnpm audit --audit-level highcleanThe release workflow's own version gate was replicated locally: six manifests and
WORKER_VERSIONall read0.2.0, andprereleaseresolvesfalse— solatestwill move on npm and both registries.One thing worth recording
The standalone bundle check initially reported 0.1.0.
dist/rsagent-worker.mjswas a stale local artifact —build:seaemits the.cjsand the executable and does not rewrite the.mjs, so it had survived from an earlier build in the same session. Rebuilt from an emptydist/, both the bundle and the SEA executable report0.2.0.CI builds from a fresh checkout so this could never have shipped, but it's a reminder that the local standalone check is worthless without clearing
dist/first.🤖 Generated with Claude Code
https://claude.ai/code/session_01AyYg2j8FVkLjiaVcj5HCkj