Skip to content
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

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

XavierChanth
Copy link
Member

- What I did

  • ADR for package upgrade solutions

- How I did it

- How to verify it

- Description for the changelog
docs: package-upgrade-solution

@XavierChanth XavierChanth requested a review from cpswan February 4, 2025 17:11
Copy link
Member

@cpswan cpswan left a 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Id est?

Copy link
Member Author

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/)
Copy link
Member

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 *

Copy link
Member Author

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.

@XavierChanth
Copy link
Member Author

We need to converge on a recommendation before proceeding with this.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants