Skip to content

experiment: studio bare-version revert only — does Windows CI go green?#780

Closed
jrusso1020 wants to merge 1 commit into
mainfrom
experiment/1-studio-bare-version-revert
Closed

experiment: studio bare-version revert only — does Windows CI go green?#780
jrusso1020 wants to merge 1 commit into
mainfrom
experiment/1-studio-bare-version-revert

Conversation

@jrusso1020
Copy link
Copy Markdown
Collaborator

This is an experiment, not intended for merge.

Testing the smallest-possible-fix hypothesis from #778's investigation. PR #748 changed studio's package.json from caret/union ranges to bare-version exact pins. If those bare-version specs are what flipped bun's resolver into a layout Windows can't materialize, this 4-line revert may be the only thing needed.

Compare to #778 (full fix: dep alignment + workflow change + source rewrites). If this experiment is green, #778 is overengineered.

Changes

…nges

Smallest-fix hypothesis test for the Windows CI regression introduced by
PR #748. That PR changed `packages/studio/package.json` from caret/union
ranges to bare-version exact pins. Reverting just those 4 lines may be
sufficient to restore the pre-PR #748 working state.

Also includes the format fix that's blocking all CI on main.
@jrusso1020
Copy link
Copy Markdown
Collaborator Author

Closing — experiment result. Reverting studio's bare-version pins alone does not fix Windows CI. Same original failure: ERR_MODULE_NOT_FOUND: Cannot find package 'esbuild' imported from packages/producer/build.mjs. The bare-version pins were not the trigger. See #778 for the working fix.

@jrusso1020 jrusso1020 closed this May 13, 2026
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