Repository navigation
fix: pin dsh.bundle.patch.yml to LF + normalize CRLF before byte-exact includes (#2631) - #2634
Merged
Merged
Conversation
…t includes (#2631) #2605's bundle test asserts byte-exact multi-line literals against the shipped dsh.bundle.patch.yml; Git-for-Windows checks it out CRLF (autocrlf) and the includes fail on every Windows leg since #2610 merged — master's test (windows-latest, 22|24) legs have been red since 07:30Z, blocking every PR's required checks (#2631). Same failure class as #1305 (golden JSONs): pin eol=lf in .gitattributes, and belt-and-suspenders normalize CRLF after read in the test so checkouts that bypass gitattributes still pass.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2847-pr.2634.7056494This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2634.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.218-master.2d31e42 # this exact build
npm install -g billion-context@master # always the newest merged build
|
YunzhouLi-hub
added a commit
to YunzhouLi-hub/billion-context
that referenced
this pull request
Oct 10, 2026
This was referenced Oct 10, 2026
Merged
Closed
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
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.
Fixes #2631
Ship-first per owner: this unblocks the v0.1.191 release PR #2630 (its Windows legs are deterministic red on current master until this lands).
What
Exactly the fix the issue proposes, nothing more:
.gitattributes:dsh.bundle.patch.yml text eol=lf— same test: wire-contract anti-regression system — parity fakes, goldens, unified ledger #1305 precedent as the golden JSONs.tests/issue2605-dsh-retry-patch.test.ts:replaceAll("\r\n", "\n")after read — belt-and-suspenders for checkouts that bypass gitattributes.Verification
dsh.bundle.patch.ymlto CRLF on disk → before the fix the bundle-lane assert fails (compaction-basic auto:false row must stay intact), after it 2/2 tests pass (bundle lane + overlay lane).§7.4 self-check
Fix-scoped, regression-proven, no config/persistence/wire/kernel surface — auto-merge eligible per §7.4 except it's on the CI-critical path during an active release; human review requested. Merge order for the release: merge THIS PR → merge master into
2026-10-10_release-v0.1.191(I'll push that immediately after) → windows legs go green → merge #2630.