chore(deps): update oven-sh/setup-bun action to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
oven-sh/setup-bun	action	major	v1 -> v2

---

Release Notes

oven-sh/setup-bun (oven-sh/setup-bun)

v2

Compare Source

oven-sh/setup-bun is the github action for setting up Bun.

This release introduces support for the bun-version-file option, fixes https://github.com/oven-sh/setup-bun/issues/79, and adds bun paths & urls to the output (https://github.com/oven-sh/setup-bun/issues/81)

For more information, see https://github.com/oven-sh/setup-bun/pull/76 by @​adeherysh and https://github.com/oven-sh/setup-bun/pull/80 by @​xHyroM 🎉

Full Changelog: oven-sh/setup-bun@v1...v2

---

Configuration

📅 Schedule: Branch creation - "before 4am on Wednesday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
eslint-config	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 10, 2024 1:16am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 51a57e8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the GitHub action to a specific commit to ensure stability Consider pinning the 'oven-sh/setup-bun' action to a specific commit rather than just the major version. This can help ensure that the workflow remains stable even if there are breaking changes or regressions introduced in newer versions of the action. .github/workflows/check.yml [16] -uses: oven-sh/setup-bun@v2 +uses: oven-sh/setup-bun@v2 # Specific commit hash e.g., @abc1234 Suggestion importance[1-10]: 9 Why: Pinning the action to a specific commit is a best practice that ensures stability and predictability by preventing unexpected changes from breaking the workflow. This suggestion is highly relevant and beneficial.	9
	Pin the GitHub action to a specific commit to ensure stability in the release process Similar to the previous suggestion, pinning the 'oven-sh/setup-bun' action to a specific commit in the 'release.yml' workflow can help maintain stability and predictability in the deployment process. .github/workflows/release.yml [30] -uses: oven-sh/setup-bun@v2 +uses: oven-sh/setup-bun@v2 # Specific commit hash e.g., @abc1234 Suggestion importance[1-10]: 9 Why: Similar to the first suggestion, pinning the action to a specific commit in the release workflow ensures stability and predictability, which is crucial for the deployment process. This is a highly relevant and beneficial suggestion.	9