Skip to content

chore(deps): update dependency bun to v1.4.2 - #241

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions-versions
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions-versions

Conversation

@renovate

@renovate renovate Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
bun (source) 1.3.141.4.2 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

oven-sh/bun (bun)

v1.4.2: Bun v1.4.2

Compare Source

To install Bun v1.4.2

curl -fsSL https://bun.sh/install | bash

# or you can use npm
# npm install -g bun

Windows:

powershell -c "irm bun.sh/install.ps1|iex"

To upgrade to Bun v1.4.2:

bun upgrade
Read Bun v1.4.2's release notes on Bun's blog
Thanks to 3 contributors!

v1.4.1

Compare Source

v1.4.0: Bun v1.4

Compare Source

To install Bun v1.4

curl -fsSL https://bun.com/install | bash

# or you can use npm
# npm install -g bun

Windows:

powershell -c "irm bun.com/install.ps1|iex"

To upgrade to Bun v1.4.0:

bun upgrade

Read the blog post: image (1)

Thank you

Bun is free, open source, and MIT-licensed. We receive a lot of contributions from the community, and we'd like to thank everyone who fixed a bug or contributed since Bun v1.3.


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • "on the 15th day of the month before 12pm"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

@greptile-apps

greptile-apps Bot commented Sep 15, 2026

Copy link
Copy Markdown

RetriggerConfidence Score: 4/5

The PR appears safe to merge, with a non-blocking package-manager pin inconsistency that should be corrected to keep local and CI environments aligned.

Findings

  1. P2 Bun Versions Are Misaligned
Fix with agent prompt
### Issue 1
.github/workflows/lint.yml:29
The workflows now use Bun 1.4.2, while `package.json` still declares `packageManager: "bun@1.3.14"`. This can lead developers and version-management tooling to use a different Bun release than the lint, test, and release jobs. Please update the declared package-manager version to match the new CI pin.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR updates the Bun runtime used by lint, test, and release workflows from 1.3.14 to 1.4.2.

  • Applies the new runtime consistently across all five CI setup locations.
  • Leaves the package-manager declaration in package.json pinned to Bun 1.3.14, creating local-versus-CI version drift.

Reviews (1) · Last reviewed commit: "chore(deps): update dependency bun to v1..."

- uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # 2.2.0
with:
bun-version: 1.3.14
bun-version: 1.4.2

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Bun Versions Are Misaligned

The workflows now use Bun 1.4.2, while package.json still declares packageManager: "bun@1.3.14". This can lead developers and version-management tooling to use a different Bun release than the lint, test, and release jobs. Please update the declared package-manager version to match the new CI pin.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/lint.yml
Line: 29

Comment:
**Bun Versions Are Misaligned**

The workflows now use Bun 1.4.2, while `package.json` still declares `packageManager: "bun@1.3.14"`. This can lead developers and version-management tooling to use a different Bun release than the lint, test, and release jobs. Please update the declared package-manager version to match the new CI pin.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants