Skip to content

[PR] fix(deps): declare mysql2 + restore registry lock URLs; land the stranded step-3 merge (#3955) - #3966

Merged
ranxianglei merged 4 commits into
masterfrom
fix-mysql2-dep
Oct 20, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
fix-mysql2-dep

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Why master is red

Two jobs have failed on master since #3946 merged, both self-inflicted by my local install flow:

  1. mysql-contract — Cannot find package 'mysql2': my npm install mysql2 --save edit to package.json was wiped by the version-restore accident (a local install had rewritten the version line; restoring it reverted the whole file). The lock kept the subtree, so the mismatch only surfaced as missing-at-install.
  2. lock-sync — 11 lock entries carried resolved URLs pointing at my local registry relay (127.0.0.1:4873); CI regenerates against npmjs.org and diffs → red. Rewritten to https://registry.npmjs.org/... (integrity hashes were already the official ones — the relay proxies bytes unchanged).

Stranded merge rescued

#3955 (step 3 — mysql hot path) was merged into its stacked base branch (2026-10-20_mysql-backend) instead of master, so master never got it. This PR merges that branch — step 3 lands here.

Verification

  • tsc 0; storage families green locally: backend-contract 6/6 (sqlite), storage-unified 14/14, replicas 4/4, export-jsonl 5/5.
  • Lock structure validated: root entry mysql2 ^3.15.3 + node_modules/mysql2 3.15.3 + 0 relay URLs.

Fixes the master CI breakage; no behavior changes beyond declaring the dependency the merged code already imports.

Async shadow facade: sqlite keeps its zero-await sync fast path byte-for-byte;
mysql rides a serial backend queue for saves (watermark deltas, reap journal,
digest sampling, 3-strike disable) with the JSON envelope as the sync read
path. Replicas/ext/GC speak async twins; admin awaits them. writerOff stays
sqlite-only. Lazy disk-index seeding for bare-id cold loads on async backends
only. MySQL e2e suite (hot path, envelope discipline, replicas/ext, restart
warm) against real MySQL 8.0; sqlite families unchanged.
[PR] storage: mysql on the proxy hot path (async shadow facade, #3388 step 3)
…he stranded step-3 merge (#3955)

master is red on two jobs since #3946 merged:
- mysql-contract: package.json lost the mysql2 dependency when a local
  version-restore accident reverted the npm install --save edit (the lock
  kept the subtree), so the service lane cannot resolve mysql2.
- lock-sync: 11 lock entries carried resolved URLs from the local install
  relay (127.0.0.1:4873); rewritten to registry.npmjs.org (integrity
  hashes were already the official ones).

Also folds in 2350797 (the #3955 merge) which was accidentally merged
into its stacked base branch (2026-10-20_mysql-backend) instead of master
— this PR lands step 3 (mysql hot path) on master.
@ranxianglei ranxianglei changed the title fix(deps): declare mysql2 + restore registry lock URLs; land the stranded step-3 merge (#3955) [PR] fix(deps): declare mysql2 + restore registry lock URLs; land the stranded step-3 merge (#3955) Oct 20, 2026
@ranxianglei
ranxianglei merged commit 1cf118e into master Oct 20, 2026
41 of 46 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: fix-mysql2-dep (5ce7f2a)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4731-pr.3966.20528a8

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr3966.tgz
npm install -g package

Install instructions are refreshed on each push.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.673-master.1cf118e (rolling master tag).

npm install -g billion-context@0.0.673-master.1cf118e  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

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.

1 participant