-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: package-upgrade-solution #229
base: trunk
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to converge on a recommendation before proceeding with this.
- dart workspaces aims to keep all package versions under its workspace in sync | ||
by resolving them centrally first. | ||
|
||
Id est, melos resolutions starts locally then centralizes on bootstrap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Id est
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
abbreviated as "i.e.", will change to "That is"
Another thing to note is the differences between tooling options for maintaining | ||
dependencies: | ||
|
||
- [melos](https://melos.invertase.dev/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Linter is whining about using -
rather than *
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we've reached a final decision, I'll update the document and fix all lint issues.
I don't mind setting aside some free time to explore option 3. It would be nice to have a tool that allows us to be in control of our own upgrade policies. |
- What I did
- How I did it
- How to verify it
- Description for the changelog
docs: package-upgrade-solution