Repository navigation
build(deps): migrate to melos 8 and pub workspaces - #22
Merged
Merged
Conversation
Melos 7 removed melos.yaml, so the workspace config and scripts now live in the root pubspec.yaml and members resolve through a single pub workspace. - move scripts and command.version/publish config from melos.yaml into the root pubspec melos: section - declare workspace: for all 7 packages and resolution: workspace in each - bump interceptly_mcp's lints dev dependency to ^6.0.0 so the shared resolution can solve flutter_lints ^6.0.0 alongside it - pin melos 8.10.0 in the ci, release and publish workflows - drop docs references to melos.yaml and generated pubspec_overrides.yaml
Tuanpluss02
changed the title
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
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.
What
Melos 7 removed
melos.yaml; this migrates the monorepo to Melos 8 + pub workspaces.melos.yamlinto the rootpubspec.yaml(workspace:+melos:),melos.yamldeletedresolution: workspaceinterceptly_mcpdev dependencylints^4.0.0 -> ^6.0.0 so the shared resolution can solveflutter_lints ^6.0.0melos 8.10.0(previously unpinnedlatest)melos.yaml/ generatedpubspec_overrides.yamlreferencesWhy
CI installed
latestwhile the repo declaredmelos: ^6.0.0and devs ran 6.3.3 — three sources of truth for the tool that decides release versions and changelogs. Matching version banners also let us drop the legacymelos.yamlpath.Verification
flutter pub getat root resolves the whole workspace + examplemelos bootstrap-> single workspace pub get, 7 packagesmelos run check-> format, analyze, 904 tests passmelos versiondry-run produces the same version table as Melos 6dart pub publish --dry-runoninterceptly_diopasses (resolution: workspaceis not leaked to pub.dev)Notes
pub getfor the whole repo. Only one conflict existed (lintsin mcp).main, which still runs the legacymelos.yamlpath.--smart-dependentsto the release command so adapters stop cascading wheninterceptly: ^X.Y.Zalready allows the new core version.