You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e76cb9b
Browse filesBrowse the repository at this point in the historyBrowse files
Fix vendored npm tarballs captured by Git LFS (#1541) (#1559)
* Start fix for #1541
Assisted-by: Claude Code:claude-opus-5-5
* Keep vendored npm tarballs out of Git LFS
A repo that LFS-tracks *.tgz committed every vendored npm-family
tarball (and each bun.lockb member mirror) as an LFS pointer, so any
checkout without LFS smudging failed its frozen install while the
vendored scan reported success.
The per-uuid .gitattributes only unset `text`. It now also unsets
`filter`, `ident` and `working-tree-encoding`, so no parent rule can
change the committed bytes. Files written by older releases still
count as ours on revert and are rewritten by the next vendored run.
Fixes#1541
Assisted-by: Claude Code:claude-opus-5-5
* Test vendored Bun tarballs survive an LFS repo
End-to-end check for #1541: with `*.tgz filter=lfs` in the project's
.gitattributes, vendor, commit, clone with GIT_LFS_SKIP_SMUDGE=1 and
run `bun install --frozen-lockfile`. The tarball must not be an LFS
object and the clone must install the patched bytes. Skips when
git-lfs is not installed.
Assisted-by: Claude Code:claude-opus-5-5
* Check mirror metadata names before reading
Review follow-ups: a Bun workspace mirror's uuid dir only reads the
.gitignore and .gitattributes it may remove, not every sibling file.
Docs note how to fix a tarball an older release already committed as
an LFS pointer (git add --renormalize after the next vendored run).
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments