Detail what to do when bumping major version of dependency #6034
Labels
dev.packages
Relates to package publishing
e2-days
Can complete in < 5 days of normal, not dedicated, work
from.page-issue
Reported in a reader-filed concern
p2-medium
Necessary but not urgent concern. Resolve when possible.
Page URL
https://dart.dev/tools/pub/dependencies/
Page source
https://github.com/dart-lang/site-www/tree/main/src/content/tools/pub/dependencies.md
Describe the problem
It would be nice for it to be spelled out what package authors are supposed to do to their package's version if they bump a major version of a dependency. Intuitively, I suspect it's to also bump the major version of their own package, but I'm second-guessing that intuition because that would have a rippling effect throughout the package ecosystem.
Expected fix
Add a sub-section to the Best Practices section on what to do to your own package's version when upgrading dependencies.
Additional context
No response
I would like to fix this problem.
The text was updated successfully, but these errors were encountered: