chore: migrate to Melos 8 (native Dart pub workspaces) - #167
Merged
Conversation
Move from Melos ^6.3.2 to ^8.2.2, which links local packages via native Dart pub workspaces instead of generated pubspec_overrides.yaml. - Root pubspec.yaml: add `workspace:` (explicit members, no globs), bump melos dev_dependency, and add the `melos:` config block (useRootAsPackage: true, workspaceChangelog: false, scripts ported verbatim). melos.yaml is removed. - Add `resolution: workspace` to all 7 packages and example. - Bump example SDK floor >=3.1.0 -> >=3.6.0 (workspace member minimum). - Remove all committed pubspec_overrides.yaml and gitignore them. They are only legal in the workspace root now, so a leftover in a member would break `melos bootstrap` on a fresh CI checkout. - CI: bump MELOS_VERSION 6.3.3 -> 8.2.2. Verified locally: single root pub get with no overrides regenerated, `melos list` sees all members, analyze/analyze:example/test pass, and pigeon contract regen produces no diff. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Melos 7+ lets a script be invoked directly as `melos <script-name>`, so CI's `melos bootstrap` executed the user script `bootstrap: dart run melos bootstrap` instead of the built-in command. That re-invoked itself, recursing infinitely and spawning dart VMs until the runner killed the job (exit code 143). In Melos 6 `melos bootstrap` was strictly the built-in, so the same script was harmless. The script was a redundant alias for the built-in command; remove it. `melos bootstrap` now runs the built-in and completes in ~2s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move from Melos ^6.3.2 to ^8.2.2, which links local packages via native Dart pub workspaces instead of generated pubspec_overrides.yaml.
workspace:(explicit members, no globs), bump melos dev_dependency, and add themelos:config block (useRootAsPackage: true, workspaceChangelog: false, scripts ported verbatim). melos.yaml is removed.resolution: workspaceto all 7 packages and example.melos bootstrapon a fresh CI checkout.Verified locally: single root pub get with no overrides regenerated,
melos listsees all members, analyze/analyze:example/test pass, and pigeon contract regen produces no diff.