Skip to content

Run CI on Bun 1.4.4 - #1165

Open
abdulwahabone wants to merge 2 commits into
mainfrom
chore/bun-1.4.4
Open

abdulwahabone wants to merge 2 commits into
mainfrom
chore/bun-1.4.4

Conversation

@abdulwahabone

@abdulwahabone abdulwahabone commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator

Bumps the pinned Bun from 1.3.13 to 1.4.4 (latest, released 2026-10-22).

  • bun install --frozen-lockfile passes on 1.4.4 with no lockfile change.
  • The renaissance-geek-inc/pristine CI already runs 1.4.4 (its setup-bun has no pin).

🤖 Generated with Claude Code


Note

Low Risk
Toolchain pin and regenerated minified asset only; no intentional logic changes to the review UI.

Overview
Pins the repo toolchain to Bun 1.4.4 by updating .bun-version from 1.3.13.

Because scripts/build-component-review.mjs only allows bundling with the pinned Bun, the tracked embed crates/context/assets/component-review.js is regenerated. The diff is almost entirely minifier output (renamed symbols); the component-review UI source is not functionally changed—CI’s bundle test still asserts the asset matches a fresh Bun.build of ui/component-review/entry.ts.

Reviewed by Cursor Bugbot for commit 607cec8. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge.

Summary

Updates the pinned Bun version from 1.3.13 to 1.4.4 and refreshes the generated component-review bundle.

  • CI jobs now follow the repository’s Bun 1.4.4 version pin.

Reviews (2) · Last reviewed commit: "Rebuild the component review bundle with..." · Reviewed by Greptile

Bun 1.4 minifies with different identifier names, so the committed bundle
no longer matched Bun.build output. Regenerated with
scripts/build-component-review.mjs; no source change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the ready to merge Passing, resolved, and ready for a maintainer merge decision label Oct 24, 2026

This branch has not been deployed

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

Labels

ready to merge Passing, resolved, and ready for a maintainer merge decision

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant