Skip to content

fix(release): 0.1.3 — doctor reads per-project port#18

Merged
Astralchemist merged 1 commit into
mainfrom
release/0.1.3
May 26, 2026
Merged

fix(release): 0.1.3 — doctor reads per-project port#18
Astralchemist merged 1 commit into
mainfrom
release/0.1.3

Conversation

@Astralchemist
Copy link
Copy Markdown
Owner

Closes #17. Published as rig-constellation@0.1.3 (latest).

Change

rig doctor was probing a hardcoded port 7474, but since 0.1.2 each project gets a stable per-project port (.rig/config.json). Doctor now resolves the port the same way serveWeb does and probes/labels that port.

  • Exported resolvePort (+ resolveProjectName) from @rig/web and reused it in doctor.ts (no duplicated config-read logic).
  • Busy-port message now notes the free-port fallback instead of sounding alarming.
  • Added __tests__/port-resolution.test.ts: resolvePort precedence (flag → config → 7474), resolveProjectName, and stablePort determinism/range.

Verification

  • bun run build, gen:check, check:compat (0 breaking), check:migrations, bun test (201 pass / 0 fail) — all green.
  • Headless: a project with stable port 7491 now shows ✓ port 7491 available for \rig serve --web``.

🤖 Generated with Claude Code

@Astralchemist Astralchemist merged commit 36da2c3 into main May 26, 2026
0 of 7 checks passed
@Astralchemist Astralchemist deleted the release/0.1.3 branch May 26, 2026 12:22
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.

doctor: check the resolved per-project port, not hardcoded 7474

1 participant