typed_data
typed_data copied to clipboard
dart-lang
Allow upcoming package:collection version 2.x
There will not be a breaking change in package:collection that concerns this package, but currently due to a circular dependency it's not even possible to bump said package's version to 2.0.
- See the CI failure in https://github.com/dart-lang/collection/pull/331
$ dart pub get
Resolving dependencies...
Because test >=1.16.0 depends on typed_data ^1.3.0 which depends on collection ^1.15.0, test >=1.16.0 requires collection ^1.15.0.
So, because collection depends on test ^1.16.0 and collection is 2.0.0-wip, version solving failed.
- [x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.
Contribution guidelines:
- See our contributor guide for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before creating a PR.
- Contributions to our repos should follow the Dart style guide and use
dart format. - Most changes should add an entry to the changelog and may need to rev the pubspec package version.
- Changes to packages require corresponding tests.
Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.
There will not be a breaking change in package:collection that concerns this package, but currently due to a circular dependency it's not even possible to bump said package's version to 2.0.
- See the CI failure in https://github.com/dart-lang/collection/pull/331
$ dart pub get Resolving dependencies... Because test >=1.16.0 depends on typed_data ^1.3.0 which depends on collection ^1.15.0, test >=1.16.0 requires collection ^1.15.0. So, because collection depends on test ^1.16.0 and collection is 2.0.0-wip, version solving failed.
collection only depends on test through a dev_dependency; it would be possible to do dependency_override of typed_data in package collection's pubspec, which would allow its CI to complete. That would mean we wouldn't have to proactively publish a version of typed_data which allows for an unpublished major version of collection.
Thanks @devoncarew. But maybe this is still simpler - why not make a proactive release? A release that increases the version range would have to be done right away anyway.