upgrade: update dependency analyzer_testing to v0.2.6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
analyzer_testing (source)	dev_dependencies	minor	0.1.9 → 0.2.6

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

dart-lang/sdk (analyzer_testing)

v0.2.6

• Require version 13.0.0 of the analyzer package.

v0.2.5

• Require version 12.1.0 of the analyzer package.

v0.2.4

• Require version 12.0.0 of the analyzer package.

v0.2.2

• Require version ^11.0.0-0 of the analyzer package.

v0.2.1

• Require version 10.3.0-dev of the analyzer package.

v0.2.0

• Remove deprecated mock APIs: MockPackagesMixin.addAngularMeta
MockPackagesMixin.addFlutterTest MockPackagesMixin.addJs
MockPackagesMixin.addKernel MockPackagesMixin.pedantic and
  MockPackagesMixin.addUI.
• Require version 10.1.0 of the analyzer package.

v0.1.10

• A stub Flutter package can be added in tests by overriding the
  addFlutterPackageDep getter to return true. This API existed before but is
  now functional; same with addFixnumPackageDep, addMetaPackageDep, and
  addTestReflectiveLoaderPackageDep.
• Require version 10.0.2 of the analyzer package.

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional flags.

[devin-ai-integration]

Devin Review found 3 new potential issues.

[devin-ai-integration]

📝 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.

[devin-ai-integration]

Devin Review found 2 new potential issues.

[devin-ai-integration]

📝 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.

[devin-ai-integration]

Devin Review found 1 new potential issue.

[devin-ai-integration]

🚩 Minor version bump within 0.x range may include breaking changes

The analyzer_testing package is being bumped from 0.1.9 to 0.2.6. Under semver conventions, for packages with a major version of 0, minor version bumps (0.1.x → 0.2.x) can include breaking API changes. All test files across the three packages use AnalysisRuleTest from package:analyzer_testing/analysis_rule/analysis_rule.dart and rely on methods like assertDiagnostics, assertNoDiagnostics, lint, setUp, getFile, newFile, and writeTestPackageConfig. If any of these APIs changed in the 0.2.x release, tests would fail. This should be verified by running the test suite (CI should catch this).

---

Was this helpful? React with 👍 or 👎 to provide feedback.