Where Does Melos Store Config and Versions?
Melos reads melos.yaml at each monorepo root for packages and scripts, with versioning state in changelogs plus .dart_tool per package.
Last updated
Melos centers Dart monorepos on melos.yaml declaring packages, scripts, and versioning behavior. Each package keeps its own pubspec while Melos orchestrates bootstrap, exec, and publish across all of them. Changelogs accumulate per package.
Local linking distinguishes Melos from plain pub workspaces. Bootstrap connects packages so changes propagate without publishing. New checkouts configure from the YAML plus pubspecs alone.
Where Melos stores this, by platform
melos.yaml + .dart_tool
Monorepo packages plus scripts config versioned at root. Bootstrap links locals together. Changelogs version per package.
melos.yaml + .dart_tool
Same repo relative config on Mac installs. Pubspecs stay per package beneath root. Versioning commands read conventional commits.
melos.yaml + .dart_tool\
Windows projects share the identical layout. Bootstrap once per checkout. Scripts run across packages uniformly.
Frequently asked questions
How do I set up Melos in a repo?
Add melos.yaml at root listing packages plus shared scripts, then bootstrap to link local versions. Versioning commands update changelogs across packages together. Commit the YAML for team consistency.
How does Melos versioning work?
Run melos version with conventional commits to bump versions and changelogs per package automatically. Independent versioning tracks each package separately. Publish flows follow the same file.
Notice an outdated path? Let us know.