Skip to content

fix: add import attribute to release-prefixes.json import#5445

Merged
lukemelia merged 1 commit into
mainfrom
fix-compute-release-json-import-attribute
Jul 9, 2026
Merged

fix: add import attribute to release-prefixes.json import#5445
lukemelia merged 1 commit into
mainfrom
fix-compute-release-json-import-attribute

Conversation

@lukemelia

Copy link
Copy Markdown
Contributor

Problem

The boxel-cli publish workflow has failed on every push to main since ~Jun 26 at its "Compute release" step:

TypeError [ERR_IMPORT_ATTRIBUTE_MISSING]: Module ".../scripts/release-prefixes.json" needs an import attribute of "type: json"

CI runs Node 24, which rejects bare JSON module imports. Because the publish pipeline is broken, no new versions of @cardstack/boxel-cli have shipped to npm since Jun 19 — including the atomic-upload positional-mapping fix (#5413) that the boxel-skills "Sync to Workspace" action needs.

Fix

Add the required import attribute to the one bare JSON import in packages/boxel-cli/scripts/:

import bumpByPrefixJson from './release-prefixes.json' with { type: 'json' };

Verification

  • Reproduced the crash locally on Node 24.17.0 (same version as CI) with the unfixed script; the fixed script runs cleanly and emits its release JSON.
  • pnpm exec vitest run tests/scripts/compute-release.test.ts — 30/30 pass.
  • eslint + prettier clean.

Note: scripts/compute-release.ts is not part of the npm or plugin bump surfaces, so this PR itself computes a no-op release; its purpose is to unbreak the workflow for subsequent merges and the promote path.

🤖 Generated with Claude Code

Node 24 rejects bare JSON imports with ERR_IMPORT_ATTRIBUTE_MISSING,
which crashed the boxel-cli publish workflow's "Compute release" step
on every push to main.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lukemelia
lukemelia merged commit b38f3da into main Jul 9, 2026
24 checks passed
@lukemelia
lukemelia deleted the fix-compute-release-json-import-attribute branch July 9, 2026 04:05
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