Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Frontend Frameworks is updating more dependencies! More details at
https://wiki.atl.workiva.net/display/CP/Dependency+Upgrades
This updates the maximum for the following packages (leaving the minimum unchanged)
pubspec_codemod raise-max build_runner 3.0.0 --recursive
pubspec_codemod raise-max crypto 4.0.0 --recursive
pubspec_codemod raise-max dart_style 3.0.0 --recursive
pubspec_codemod raise-max dependency_validator 4.0.0 --recursive
pubspec_codemod raise-max io 2.0.0 --recursive
pubspec_codemod raise-max mime 2.0.0 --recursive
pubspec_codemod raise-max quiver 4.0.0 --recursive
pubspec_codemod raise-max stream_transform 3.0.0 --recursive
pubspec_codemod raise-max tuple 3.0.0 --recursive
pubspec_codemod raise-max uuid 4.0.0 --recursive
pubspec_codemod raise-max yaml 4.0.0 --recursive
How do we know these ranges are safe?
build_runner
,dart_style
, anddependency_validator
are all only used for their executables and shouldn't introduce any breaking changes. Note that as your package resolves to newer versions ofdart_style
, it's possible that you may need to commit some updated formatting changes.crypto
v3 is the NNBD migration and has one breaking change, which is to remove anewInstance()
method on some classes. We have no usages of this method.io
v1,mime
v1,stream_transform
v2, andtuple
v2 are all NNBD migrations.quiver
v3 has breaking changes, so we ran a batch change with a dependency override to verify compatibility. We did identify one package affected by these breaking changes, which has already been remediated.uuid
v2 and v3 have some breaking changes, so we ran a batch change with a dependency override to verify compatibility We identified and fixed 1 test that was affected by the uuid change.yaml
v3 has one breaking change, which is that optionalsourceUrl
param in theloadYaml
function is now typed asUri
instead ofdynamic
(previously it allowedString
, as well). We have already addressed our own usages of this parameter to useUri
s.While we're confident these newer versions should be safe to consume, we can't say for sure. Please reach out to us if you encounter any issues that you think may be related.
For more info, reach out to
#support-frontend-architecture
on Slack.Created by Sourcegraph batch change
Workiva/raise_more_max_versions
.