upgrade: update dependency analyzer_testing to v0.2.4#440
upgrade: update dependency analyzer_testing to v0.2.4#440renovate[bot] wants to merge 1 commit intomainfrom
Conversation
e007279 to
3542dcb
Compare
3542dcb to
f4c9b7e
Compare
f4c9b7e to
6f03766
Compare
6f03766 to
8fddd1b
Compare
There was a problem hiding this comment.
📝 Info: Deprecated API pattern in use - analysisRule getter
The release notes for analyzer_testing v0.1.7 state: "Deprecate AnalysisRuleTest.analysisRule; instead of implementing this getter, set the rule field in the setUp method, before calling super.setUp."
All test files in this project use the deprecated pattern, for example in packages/nilts/test/unstable_enum_name_test.dart:114:
@override
String get analysisRule => UnstableEnumName.ruleName;This is found in 19 test files. While deprecated APIs typically continue to work, upgrading to 0.1.10 will likely produce deprecation warnings during test runs. Consider updating to the new pattern (rule = MyRule() in setUp before super.setUp()) to stay current with the library's conventions.
Was this helpful? React with 👍 or 👎 to provide feedback.
8fddd1b to
5bb4980
Compare
packages/nilts_clock/pubspec.yaml
Outdated
|
|
||
| test: 1.26.3 | ||
| analyzer_testing: 0.1.5 | ||
| analyzer_testing: 0.2.1 |
There was a problem hiding this comment.
📝 Info: All three packages updated consistently
I verified that all three packages (nilts, nilts_clock, nilts_flutter_hooks) were updated from 0.1.5 to 0.2.1 consistently. The fourth workspace member (nilts_core at packages/nilts_core/pubspec.yaml) does not depend on analyzer_testing and is not affected. The workspace root pubspec.yaml also does not list analyzer_testing. So the change is consistent across the repo — this is not a bug, just confirmation that no package was missed.
Was this helpful? React with 👍 or 👎 to provide feedback.
5bb4980 to
4678fa1
Compare
4678fa1 to
4738ab6
Compare
4738ab6 to
c89b49a
Compare
This PR contains the following updates:
0.1.7→0.2.4Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dart-lang/sdk (analyzer_testing)
v0.2.4Compare Source
12.0.0of theanalyzerpackage.v0.2.2Compare Source
^11.0.0-0of theanalyzerpackage.v0.2.1Compare Source
10.3.0-devof theanalyzerpackage.v0.2.0MockPackagesMixin.addAngularMetaMockPackagesMixin.addFlutterTestMockPackagesMixin.addJsMockPackagesMixin.addKernelMockPackagesMixin.pedanticandMockPackagesMixin.addUI.10.1.0of theanalyzerpackage.v0.1.10addFlutterPackageDepgetter to returntrue. This API existed before but isnow functional; same with
addFixnumPackageDep,addMetaPackageDep, andaddTestReflectiveLoaderPackageDep.10.0.2of theanalyzerpackage.v0.1.9MockPackagesMixin.addUI; This is replaced byaddSkyEngine.MockPackagesMixin.addFlutterTest. A mockflutter_testpackagecan still be written with
PubPackageResolutionTest.newPackage.10.0.1of theanalyzerpackage.v0.1.810.0.0of theanalyzerpackage.analysisOptionsContentso that by default, theanalysis options file used in testing specifies a
truevalue forpropagate-linter-exceptions. This ensures that when tests are run,exceptions that occur while processing lint rules will cause the test to fail.
MockPackagesMixin.addAngularMeta. A mockangular_metapackagecan still be written with
PubPackageResolutionTest.newPackage.MockPackagesMixin.addJsandPubPackageResolutionTest.addJsPackageDep. A mock js package can still bewritten with
PubPackageResolutionTest.newPackage.MockPackagesMixin.addKernelandPubPackageResolutionTest.addKernelPackageDep. A mock kernelpackage can still be written with
PubPackageResolutionTest.newPackage.MockPackagesMixin.addPedantic. A mock pedantic package can stillbe written with
PubPackageResolutionTest.newPackage.Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.