-
-
Notifications
You must be signed in to change notification settings - Fork 644
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.
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
feat(ci): ⚡ add Bun packages caching feature in workflows #2637
Conversation
Signed-off-by: Okinea Dev <[email protected]>
Pull request was closed
Maybe it is worth using the latest version of Bun in workflows? Because every update brings speed improvements and bug fixes, I understand that for stability reasons you want to manually specify the bun version, but it's hard to keep track of and update the bun version manually |
While using the latest version of Bun can provide speed improvements and bug fixes, there are trade-offs to consider, especially regarding stability. Automatically updating to the latest version in workflows could introduce unexpected issues, breaking existing functionality or workflows if a new version has unforeseen bugs or changes. Manually specifying a version ensures stability and consistency across environments, allowing for testing before applying updates. Tracking versions manually may seem cumbersome, but it offers more control and avoids potential downtime or complications from an untested update. |
I think I heard about the `.bun-version| file, I'll try to figure it out tomorrow |
why |
I a) wanted to use some features bun didn't support and b) preferred a more easily diffable lockfile |
what do you use |
node, pnpm for the projects I used bun in (+deno deploy), deno for new projects |
ok |
Description
Bun package caching has been added for faster execution of workflows
Contribution Guidelines