Skip to content
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

Closed
wants to merge 3 commits into from

Conversation

okineadev
Copy link
Contributor

Description

Bun package caching has been added for faster execution of workflows

Contribution Guidelines

@github-actions github-actions bot added the workflows GitHub Actions label Oct 29, 2024
@okineadev okineadev enabled auto-merge (squash) October 29, 2024 11:18
@okineadev okineadev requested a review from lucas-labs October 29, 2024 11:19
@okineadev okineadev closed this Oct 29, 2024
auto-merge was automatically disabled October 29, 2024 13:21

Pull request was closed

@okineadev
Copy link
Contributor Author

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

@PKief
Copy link
Member

PKief commented Oct 29, 2024

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.

@okineadev
Copy link
Contributor Author

I think I heard about the `.bun-version| file, I'll try to figure it out tomorrow

@lishaduck
Copy link
Contributor

What I do/did was to subscribe to bun's RSS feed.1

Footnotes

  1. I don't use bun anymore, but I'm still subscribed, waiting for various improvements.

@okineadev
Copy link
Contributor Author

don't use bun anymore

why

@lishaduck
Copy link
Contributor

don't use bun anymore

why

I a) wanted to use some features bun didn't support and b) preferred a more easily diffable lockfile

@okineadev
Copy link
Contributor Author

don't use bun anymore

why

I a) wanted to use some features bun didn't support and b) preferred a more easily diffable lockfile

what do you use

@lishaduck
Copy link
Contributor

what do you use

node, pnpm for the projects I used bun in (+deno deploy), deno for new projects

@okineadev
Copy link
Contributor Author

what do you use

node, pnpm for the projects I used bun in (+deno deploy), deno for new projects

ok

@okineadev okineadev deleted the bun-deps-caching-feature branch November 5, 2024 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflows GitHub Actions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants