search

invertase / melos

🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.
https://melos.invertase.dev/~melos-latest
Apache License 2.0
1.11k stars 198 forks source link

request: support for not specify versions of internal packages #609

Closed lohnn closed 9 months ago

lohnn commented 9 months ago

Is there an existing feature request for this?

Command

No response

Description

It would be nice if melos bs had the option to specify versions of private/internal dependencies as any in pubspec.yaml.

Reasoning

We have multiple internal packages in our monorepo for our closed source application, and every time we build a release build all pubspec.yaml files are updated with the new dependency versions.

Since this application is, and will continue to be, closed source we don't really care about the version numbers of our internal packages in the dependencies as they are overridden with path dependency anyways, and it only gives us headache when trying to merge PRs and we get conflicts in files we haven't (as developers) even touched ourselves.

Additional context and comments

We still want the versioning of the packages to exist, as it is a great way for us to keep track of our work, so this feature request is only for the option to change how dependencies are specified.

lohnn commented 9 months ago

Also, I can take a stab at implementing this as soon as we have a solution proposal.

spydon commented 9 months ago

We're discussing this outside of GitHub, I'll triage this when we've cleared up some things.

lohnn commented 9 months ago

Nevermind, we had specified a version in the shared dependencies config in melos.yaml and by just specifying version as any it works just as I wished. Closing this, thanks @spydon!