Update dependency package_info_plus to v9 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
package_info_plus (source)	dependencies	major	^8.3.0 → ^9.0.0

---

Warning

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

---

Release Notes

fluttercommunity/plus_plugins (package_info_plus)

v9.0.0

Compare Source

Note: This release has breaking changes.

On Android plugin now requires the following:

• Android Gradle Plugin >=8.12.1
• Gradle wrapper >=8.13
• Kotlin 2.2.0

• DOCS(all): replace MacOS by macOS in package READMEs (#​3658). (72b6234c)
• BREAKING FEAT(package_info_plus): Change Android compile SDK, update Android build config (#​3674). (78c2b742)

---

Configuration

📅 Schedule: (in timezone Europe/Warsaw)

• Branch creation
  • At any time (no schedule defined)
• 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: client/pubspec.lock

Command failed: flutter pub upgrade package_info_plus
Note: matcher is pinned to version 0.12.19 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Note: test_api is pinned to version 0.7.11 by flutter_test from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

The current Dart SDK version is 3.12.2.

    Because test >=1.16.0-nullsafety.8 <1.16.5 depends on io ^0.3.0 and build_verify >=3.0.0 depends on io ^1.0.0, test >=1.16.0-nullsafety.8 <1.16.5 is incompatible with build_verify >=3.0.0.
    And because build_verify >=2.0.0 <3.1.1 depends on test ^1.0.0 and no versions of build_verify match >3.1.1 <4.0.0, build_verify >=3.0.0 <3.1.1-∞ or >3.1.1 <4.0.0 requires test >=1.0.0 <1.16.0-nullsafety.8 or >=1.16.5 <2.0.0.
(1) So, because build_verify 3.1.1 depends on test ^1.16.6 and test >=0.12.0-beta.3 <1.16.0-nullsafety.8 doesn't support null safety, build_verify ^3.0.0 requires test ^1.16.5.

    Because test >=1.31.0 <1.31.1 depends on analyzer >=8.0.0 <13.0.0 and test >=1.21.6 <1.24.4 depends on analyzer >=2.0.0 <6.0.0, test >=1.21.6 <1.24.4-∞ or >=1.31.0 <1.31.1-∞ requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0.
    And because test >=1.21.0 <1.21.6 depends on analyzer >=2.0.0 <5.0.0, test >=1.21.0 <1.24.4-∞ or >=1.31.0 <1.31.1-∞ requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0.
    And because test >=1.28.0 <1.30.0 depends on matcher >=0.12.16 <0.12.19 and test >=1.25.13 <1.28.0 depends on matcher >=0.12.16 <0.12.18, test >=1.21.0 <1.24.4-∞ or >=1.25.13 <1.30.0-∞ or >=1.31.0 <1.31.1-∞ requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0 or matcher >=0.12.16 <0.12.19.
    And because test >=1.24.3 <1.25.13 depends on matcher >=0.12.16 <0.12.17 and test >=1.31.2 depends on test_api 0.7.13, test >=1.21.0 <1.30.0-∞ or >=1.31.0 <1.31.1-∞ or >=1.31.2 requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0 or matcher >=0.12.16 <0.12.19 or test_api 0.7.13.
(2) So, because test >=1.31.1 <1.31.2 depends on test_api 0.7.12 and test >=1.30.0 <1.31.0 depends on test_api 0.7.10, test >=1.21.0 requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0 or matcher >=0.12.16 <0.12.19 or test_api 0.7.10 or 0.7.12 or 0.7.13.

    Because test >=1.16.6 <1.17.10 depends on analyzer ^1.0.0 and test >=1.17.10 <1.20.0 depends on analyzer >=1.0.0 <3.0.0, test >=1.16.6 <1.20.0 requires analyzer >=1.0.0 <3.0.0.
    And because test >=1.20.0 <1.21.2 depends on test_api 0.4.9, test >=1.16.6 <1.21.2 requires analyzer >=1.0.0 <3.0.0 or test_api 0.4.9.
    And because test >=1.21.0 requires analyzer >=2.0.0 <6.0.0 or >=8.0.0 <13.0.0 or matcher >=0.12.16 <0.12.19 or test_api 0.7.10 or 0.7.12 or 0.7.13 (2), test >=1.16.6 requires analyzer >=1.0.0 <6.0.0 or >=8.0.0 <13.0.0 or matcher >=0.12.16 <0.12.19 or test_api 0.4.9 or 0.7.10 or 0.7.12 or 0.7.13.
    And because every version of flutter_test from sdk depends on matcher 0.12.19, if test >=1.16.6 and flutter_test from sdk then analyzer >=1.0.0 <6.0.0 or >=8.0.0 <13.0.0 or test_api 0.4.9 or 0.7.10 or 0.7.12 or 0.7.13.
    And because build_verify ^3.0.0 requires test ^1.16.5 (1), if build_verify ^3.0.0 and flutter_test from sdk then analyzer >=1.0.0 <6.0.0 or >=8.0.0 <13.0.0 or test_api 0.4.9 or 0.7.10 or 0.7.12 or 0.7.13 or test >=1.16.5 <1.16.6.
    And because test >=1.16.1 <1.16.6 depends on analyzer >=0.39.5 <2.0.0, if build_verify ^3.0.0 and flutter_test from sdk then analyzer >=0.39.5 <6.0.0 or >=8.0.0 <13.0.0 or test_api 0.4.9 or 0.7.10 or 0.7.12 or 0.7.13.
    And because riverpod_lint 2.6.5 depends on analyzer ^7.0.0 and no versions of riverpod_lint match >2.6.5 <3.0.0, if build_verify ^3.0.0 and flutter_test from sdk and riverpod_lint ^2.6.5 then test_api 0.4.9 or 0.7.10 or 0.7.12 or 0.7.13.
    And because mobile depends on flutter_test from sdk which depends on test_api 0.7.11, build_verify ^3.0.0 is incompatible with riverpod_lint ^2.6.5.
    So, because mobile depends on both build_verify ^3.1.0 and riverpod_lint ^2.6.5, version solving failed.

The lower bound of "sdk: '>=1.8.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety


You can try the following suggestion to make the pubspec resolve:
* Try an upgrade of your constraints: flutter pub upgrade --major-versions
Failed to update packages.