Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 0 additions & 1 deletion .bun-version

This file was deleted.

2 changes: 1 addition & 1 deletion .github/actions/prepare/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ runs:
steps:
- uses: oven-sh/setup-bun@v2
with:
bun-version-file: .bun-version
bun-version-file: package.json

- name: Turbo Cache
uses: actions/cache@v5
Expand Down
4 changes: 2 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,9 +53,9 @@ Releases are automated and driven by Conventional Commits:

## Bun version

The Bun version is pinned in `.bun-version` — the version the repo develops and builds against. Keep `packageManager` in the root `package.json` in sync with it.
The Bun version is pinned in the root `package.json`'s `packageManager` — the version the repo develops and builds against. CI reads this pin directly from `package.json`.

`engines.bun` in `packages/bun-sqlgen/pkg/package.json` is a separate decision: it's the oldest Bun the published package still runs on, not the version we build with. Raise it only when the package actually depends on a newer runtime — bumping it in lockstep with `.bun-version` drops users who could otherwise install fine.
`engines.bun` in `packages/bun-sqlgen/pkg/package.json` is a separate decision: it's the oldest Bun the published package still runs on, not the version we build with. Raise it only when the package actually depends on a newer runtime — bumping it in lockstep with `packageManager` drops users who could otherwise install fine.

## Pull requests

Expand Down
Loading