fix(connect): seed missing config under mutation lock to avoid bootstrap race - #408
fix(connect): seed missing config under mutation lock to avoid bootstrap race#408luvs01 wants to merge 20 commits into
Conversation
release: promote dev into main for v2.32.1
# Conflicts: # package.json
[WRONG BRANCH] merge dev into main for the v2.33.0 release
Promotes the dev integration line onto main. The resulting tree is byte-identical to origin/dev, including package.json at 2.34.0. The package.json conflict is resolved to dev's side, NOT to main's stale 2.33.0. Earlier promotions (lidge-jun#2553, lidge-jun#2507) kept the target's version so the release bump would land on its own "release: vX.Y.Z" commit. That is no longer legal: this very delta adds tests/release-version-line.test.ts, which fails when the in-tree version sits behind the highest release tag. With v2.34.0-preview.20260827 now published, 2.33.0 orders behind it, so a promotion carrying the stale line turns CI red on every shard that runs the suite. The consequence for the release step is that scripts/release.ts skips the bump (release.ts:568, currentVersion === version), so v2.34.0 gets tagged on this merge commit rather than on a separate release commit. The workflow creates the tag itself after publishing and validates expected-sha against the checked-out commit, so the tag still names exactly the audited tree.
[WRONG BRANCH] promote dev onto main for v2.34.0
[WRONG BRANCH] promote dev onto main for v2.35.0
[WRONG BRANCH] promote dev onto main for v2.36.0
[WRONG BRANCH] promote dev to main for the v2.37.0 release
[WRONG BRANCH] promote dev onto main for v2.38.0
[WRONG BRANCH] promote dev onto main for v2.39.0
release: promote dev to main for v2.40.0
…rkflow call (lidge-jun#3262) Both v2.40.0 release dispatches (33615174183 preview, 33615177849 main) died at startup_failure: a workflow_call cannot grant its callee more than the calling job holds, and dev-version-bump.yml's job declares contents+pull- requests write. lidge-jun#3129 wired the call but never dispatched a release, so this is its first live run. The caller job now declares exactly the callee's two permissions; no other job in release.yml gains anything. Co-authored-by: jun <jun@lidge.dev> (cherry picked from commit 7ce0ba5)
…400-relfix release: carry the release.yml permissions fix onto main for v2.40.0
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
✅ Deterministic PR hygiene checks passed. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ READY
Hygiene✅ Deterministic PR hygiene checks passed. |
Motivation
config.jsonand later wrote factory defaults outside the shared mutation transaction, which could overwrite a concurrently created valid config and erase sensitive settings.Description
PersistedConfigMutationOptionswithcreateIfMissingtomutatePersistedConfigand a test hooksetPersistedConfigMutationBeforeLockForTeststo cover the pre-lock race window.mutatePersistedConfigto acceptoptions?: PersistedConfigMutationOptions, invoke a before-lock test hook, acquire the shared mutation lock, re-read the persisted snapshot, and only create+persist factory defaults while holding the lock when the file is still genuinely absent; malformed config still fails closed.commitClientConnectionto callmutatePersistedConfig(..., { createIfMissing: getDefaultConfig })instead of doing an unlockedsaveConfigfallback, so bootstrap defaults are created inside the mutation transaction and any concurrently written top-level fields are preserved or rebased.tests/client-connect.test.tsthat injects a competingsaveConfigjust before lock acquisition and verifies that listener settings, admission keys, and the new client block are preserved (and that the outcome iscommitted).Testing
./node_modules/bun/bin/bun.exe test tests/client-connect.test.ts, which passed (20 tests, 0 failures).bun x tsc --noEmitwhich succeeded.bun run privacy:scanwhich passed.git diff --checkand the focused file diffs; a fullbun run testwas started but encountered unrelated pre-existing lab/timeouter and server-auth expectations in unrelated tests during a long parallel run (the fix was validated by the focused suite above).Codex Task