chore: pin bun 1.3.11 via .tool-versions - #202
Conversation
|
@codex review |
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 913f727bf7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Context
When I first cloned the repo and looked up
bun.lockI knew that it uses bun, however, when I installed the deps, I got anotherbun.lockbbecause I was on the wrong version of bun.Because at bunny you use
asdf, I added.tool-versionsfile to confirm what version it is and works withasdfandmisetoo (this is what I use).One downside, is that:
asdfdoesn't support version ranges, wild cards, or minor version, the version has to be exact. Therefore I pined the version to1.3.11as it's the same used in the CI for a minimum change. I tested it it works on asdf.This is my sandbox for testing asdf, since I use mise. The binary of asdf (https://github.com/asdf-vm/asdf/releases/download/v0.20.0/asdf-v0.20.0-darwin-arm64.tar.gz) was inside that directory.