Skip to content

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

  • upgrade to bun v1.3

Type of Change

  • Other: deps

Testing

Tested manually

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel
Copy link

vercel bot commented Dec 4, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Dec 4, 2025 8:44am

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Dec 4, 2025

Greptile Overview

Greptile Summary

Upgraded Bun from v1.2.22 to v1.3.3 across all environments and CI/CD pipelines.

  • Updated packageManager field in package.json from 1.2.12 to 1.3.3
  • Updated all Docker base images (app, db, realtime, devcontainer) to use oven/bun:1.3.3-alpine
  • Updated Bun version in all 7 GitHub workflow files to 1.3.3
  • bun.lock updated with new configVersion: 0 field

This is a straightforward dependency upgrade with consistent version updates across all configuration files.

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk
  • This is a clean dependency upgrade with consistent version bumps across all configuration files. The changes are mechanical and cover all necessary locations (package.json, Dockerfiles, CI workflows, devcontainer). The lockfile update adds only the expected configVersion field. The developer has tested manually per the PR description.
  • No files require special attention

Important Files Changed

File Analysis

Filename Score Overview
.devcontainer/Dockerfile 5/5 Updated Bun version from 1.2.22 to 1.3.3 in devcontainer base image
bun.lock 5/5 Added configVersion: 0 field to lockfile metadata
docker/app.Dockerfile 5/5 Updated Bun version from 1.2.22 to 1.3.3 in base image
docker/db.Dockerfile 5/5 Updated Bun version from 1.2.22 to 1.3.3 in base image
docker/realtime.Dockerfile 5/5 Updated Bun version from 1.2.22 to 1.3.3 in base image
package.json 5/5 Updated packageManager field from bun@1.2.12 to bun@1.3.3

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PM as package.json
    participant Lock as bun.lock
    participant GH as GitHub Workflows
    participant Docker as Docker Images
    participant DevC as DevContainer

    Dev->>PM: Update packageManager to bun@1.3.3
    Dev->>Lock: Run bun install
    Lock-->>Lock: Add configVersion: 0
    
    Dev->>GH: Update all workflows
    Note over GH: docs-embeddings.yml<br/>i18n.yml (2 jobs)<br/>migrations.yml<br/>publish-cli.yml<br/>publish-ts-sdk.yml<br/>test-build.yml
    GH-->>GH: Set bun-version: 1.3.3
    
    Dev->>Docker: Update Dockerfiles
    Note over Docker: app.Dockerfile<br/>db.Dockerfile<br/>realtime.Dockerfile
    Docker-->>Docker: FROM oven/bun:1.3.3-alpine
    
    Dev->>DevC: Update devcontainer
    DevC-->>DevC: FROM oven/bun:1.3.3-alpine
    
    Note over Dev,DevC: All environments now use Bun 1.3.3
Loading

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Additional Comments (1)

  1. package.json, line 3 (link)

    syntax: packageManager field still references bun@1.2.12 but this PR upgrades to 1.3.3. Update to match.

10 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

@waleedlatif1
Copy link
Collaborator Author

@greptile

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

11 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

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.

2 participants