Skip to content

acs-admin: refresh bun.lock to unblock the release build - #740

Merged
AlexGodbehere merged 1 commit into
mainfrom
ago/fix-acs-admin-bun-lock
Aug 27, 2026
Merged

acs-admin: refresh bun.lock to unblock the release build#740
AlexGodbehere merged 1 commit into
mainfrom
ago/fix-acs-admin-bun-lock

Conversation

@AlexGodbehere

Copy link
Copy Markdown
Contributor

What this fixes

The v6.9.0-rc.1 release run failed in build-x86-js (acs-admin) with:

error: lockfile had changes, but lockfile is frozen

acs-admin/package.json declares @internationalized/date (added with the
Calendar component) and a typescript devDependency, but bun.lock was never
regenerated. The Dockerfile runs bun install --production --frozen-lockfile,
which refuses the drift and fails the build.

This commit regenerates the lockfile. The only change is two entries added to
the workspace block; no dependency versions move.

How to test

  1. cd acs-admin
  2. bun install --production --frozen-lockfile
  3. It completes instead of erroring.

acs-edge/bun.lock was checked too and is already in sync.

Release notes

Fixed the acs-admin container build failing on an out-of-date bun.lock.

package.json gained @internationalized/date (Calendar component) and a
typescript devDependency, but bun.lock was never regenerated. The image
build runs bun install --frozen-lockfile, so it refused the drift and
failed the v6.9.0-rc.1 release run.
@AlexGodbehere
AlexGodbehere merged commit 2e0ab62 into main Aug 27, 2026
1 check passed
@AlexGodbehere
AlexGodbehere deleted the ago/fix-acs-admin-bun-lock branch August 27, 2026 10:43
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