Skip to content

Pin the Bun version for Render - #17

Closed
sleipner01 wants to merge 1 commit into
mainfrom
pin-bun-version
Closed

sleipner01 wants to merge 1 commit into
mainfrom
pin-bun-version

Conversation

@sleipner01

Copy link
Copy Markdown
Owner

Render's deploy failed with lockfile had changes, but lockfile is frozen. The service was created before August 2025, so Render defaults it to Bun 1.1.0, which can't read the text bun.lock format.

  • Add .bun-version with 1.4.2. Render reads this file from the repo root.
  • Point the CI setup action at .bun-version and drop packageManager, so the version is pinned in one place.
  • Mention the file in the README and the deployment docs.

Testing

bun install --frozen-lockfile passes locally, and CI runs on this PR. The Render deploy itself can only be verified after merging.

🤖 Generated with Claude Code

Render reads the Bun version from .bun-version and otherwise falls back
to a default based on the service's creation date. For this service
that is Bun 1.1.0, which can't read the text bun.lock format, so the
frozen install failed. CI now reads the same file, and packageManager
is dropped so the version lives in one place.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@vercel

vercel Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
bingewatcher_client Ready Ready Preview Sep 26, 2026 11:00am UTC

This branch was successfully deployed

1 active deployment
Preview — e7c06bc4 Deployed Sep 26, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant