🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.
On A depends package B and this B package has an example app. Now when I add some package, e.g. equatable to package A, and when I run melos bootstrap that equatable gets modified in pubspec.lock in example of package B.
This causes bump version of also package B, even though change is only inside example.
Drop last commit and run melos version --message="chore: update packages [skip ci]" --no-dependent-constraints --no-dependent-versions --no-git-tag-version --yes
Notice that project_b version gets bumped even though change was made only inside example folder
Is there an existing issue for this?
Version
6.1.0
Description
See Discord discussion https://discord.com/channels/295953187817521152/1059839794760392734/threads/1259616978910445638
On A depends package B and this B package has an example app. Now when I add some package, e.g. equatable to package A, and when I run melos bootstrap that equatable gets modified in pubspec.lock in example of package B.
This causes bump version of also
package B, even though change is only insideexample.Steps to reproduce
Clone https://github.com/mzdm/monorepo_example_bug
Drop last commit and run
melos version --message="chore: update packages [skip ci]" --no-dependent-constraints --no-dependent-versions --no-git-tag-version --yesNotice that
project_bversion gets bumped even though change was made only insideexamplefolderExpected behavior
project_bshould not be versionedScreenshots
No response
Additional context and comments
No response