Skip to content

chore: track bun.lock so --frozen-lockfile means something #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rahlk merged 1 commit into from
Aug 31, 2026
+552 −1
Merged

chore: track bun.lock so --frozen-lockfile means something #108

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,8 @@ node_modules/
dist/
*.tsbuildinfo
.codeanalyzer/
bun.lock
# bun.lock is TRACKED (#107): CI runs `bun install --frozen-lockfile`, which is a silent
# no-op without it. bun.lockb is the superseded binary format and stays out.
bun.lockb
.DS_Store
# The PyPI long-description is the repo root README, copied in by build_wheels.sh at build time
Expand Down
Loading
Loading