Skip to content

fix: normalize path separators in the family-gate allowlist lookup (#1629) - #1630

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-29_family-gate-path-sep
Sep 29, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-29_family-gate-path-sep

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Fixes #1629

One line: rel.split(path.sep).join("/") after path.relative, so the allowlist keys (src/conflict-watch.ts, src/text-safe.ts) match on Windows too.

…1629)

path.relative yields backslash-separated keys on Windows while the
allowlist uses forward slashes — every allowlisted entry missed and the
gate reported already-approved array-receiver slices as offenders,
turning the Windows CI legs red repo-wide since #1626.

Fixes #1629
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-29_family-gate-path-sep (9331446)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1574-pr.1630.445371f

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-pr1630.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 08ad056 into master Sep 29, 2026
12 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-29_family-gate-path-sep branch October 15, 2026 05:32
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.

family gate (tests/text-safe.test.ts) fails on Windows: path separator mismatch against the allowlist keys

1 participant