Allow analyzer 11.x and 12.x releases

[ThexXTURBOXx]

Allow analyzer 11.x and 12.x releases

Summary by CodeRabbit

• Chores
  • Updated analyzer dependency constraints in freezed and freezed_lint packages to support a broader range of compatible versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the analyzer dependency constraint in two Dart packages (freezed and freezed_lint) from >=9.0.0 <11.0.0 to >=9.0.0 <13.0.0, expanding compatibility with newer analyzer versions while maintaining backward compatibility.

Changes

Cohort / File(s)	Summary
Analyzer Dependency Updates packages/freezed/pubspec.yaml, packages/freezed_lint/pubspec.yaml	Widened analyzer version constraint from <11.0.0 to <13.0.0 in both packages, allowing support for analyzer versions up to 13.x.

Possibly related PRs

• Update analyzer 8 #1301: Modifies the analyzer dependency constraint in packages/freezed_lint/pubspec.yaml, suggesting ongoing version compatibility alignment efforts.

Poem

🐰 A dependency hop, a version bound freed,
From eleven to thirteen, just what we need,
The analyzer grows, our packages align,
Wider windows for compatibility to shine! ✨

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly reflects the main change: updating the analyzer dependency constraint to allow versions 11.x and 12.x across both pubspec.yaml files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/freezed_lint/pubspec.yaml`:
- Around line 12-14: Update the dependency constraints in pubspec.yaml to
versions compatible with the analyzer range (>=9.0.0 <13.0.0): change
custom_lint_builder from ^0.8.0 to >=0.8.1 (or a newer non-breaking release) and
change analyzer_plugin from ^0.13.0 to >=0.14.0 (or newer) so they support
analyzer 11.x/12.x; after updating the custom_lint_builder and analyzer_plugin
entries run pub get and verify the lockfile to ensure the new versions resolve
against the analyzer constraint.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 24424b8c-9167-46fb-9d23-8f7f54e348ea

📥 Commits

Reviewing files that changed from the base of the PR and between 8976ee9 and 1a61811.

📒 Files selected for processing (2)

• packages/freezed/pubspec.yaml
• packages/freezed_lint/pubspec.yaml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Has invertase/dart_custom_lint#300 been resolved?

💡 Result:

No, invertase/dart_custom_lint#300 has not been resolved. No evidence of issue or pull request #300 exists in the repository. The issues list shows issues up to #383, but #300 is absent from search results, issues pages, and specific queries. The repository was archived on Mar 24, 2026, and is read-only, but no record of #300 was found across multiple searches targeting GitHub pages, issues, and PRs.

Citations:

• 1: https://github.com/invertase/dart_custom_lint/issues
• 2: https://github.com/invertase/dart_custom_lint
• 3: https://github.com/invertase/dart_custom_lint/pulls
• 4: I want to create a custom_lint for checking unused public classes invertase/dart_custom_lint#305

---

🌐 Web query:

Does custom_lint_builder 0.8.0 support analyzer 11.x and 12.x?

💡 Result:

No, custom_lint_builder 0.8.0 does not support analyzer 11.x or 12.x. It constrains analyzer to ^7.5.0, which resolves to versions like 7.6.0 but explicitly does not support the stable analyzer 8.0.0 or higher (including 11.x and 12.x). Pub.dev score analysis confirms: "The constraint ^7.5.0 on analyzer does not support the stable version 8.0.0." Changelogs show support added incrementally up to analyzer 8.0.0 in version 0.8.1 (published 2025-09-09), but 0.8.0 (2025-07-25) only supports up to 7.5.0. Current analyzer is at 12.x as of 2026.

Citations:

• 1: https://pub.dev/packages/custom_lint_builder/versions/0.8.0/score
• 2: https://pub.dev/packages/custom_lint_builder/versions/0.8.0/changelog
• 3: https://pub.dev/packages/custom_lint_builder/changelog
• 4: https://pub.dev/packages/analyzer/versions/6.11.0
• 5: https://pub.dev/packages/analyzer/versions

---

🌐 Web query:

Does analyzer_plugin 0.13.0 support analyzer 11.x and 12.x?

💡 Result:

No, analyzer_plugin 0.13.0 does not support analyzer 11.x or 12.x. It supports analyzer 7.x versions. Subsequent releases like 0.13.1 require 7.4.x, 0.13.5 requires ^8.0.0, 0.13.11 requires 9.0.0, and 0.14.x requires 10.x-12.x. There was a known incompatibility with analyzer 7.4.5 fixed in 0.13.1.

Citations:

• 1: https://pub.dev/packages/analyzer_plugin/versions/0.13.10/changelog
• 2: Compatibility issue with analyzer_plugin 0.13.0 and analyzer 7.4.5 dart-lang/sdk#60899
• 3: https://dart.googlesource.com/sdk/+/refs/heads/base/pkg/analyzer_plugin/CHANGELOG.md
• 4: https://pub.dev/packages/analyzer_plugin/changelog

---

🏁 Script executed:

#!/bin/bash
# Check dependency version constraints

echo "=== Checking custom_lint_builder pubspec ==="
curl -s https://pub.dev/api/packages/custom_lint_builder | jq -r '.latest.pubspec.dependencies.analyzer // "not found"'

echo -e "\n=== Checking analyzer_plugin pubspec ==="
curl -s https://pub.dev/api/packages/analyzer_plugin | jq -r '.latest.pubspec.dependencies.analyzer // "not found"'

Repository: rrousselGit/freezed

Length of output: 163

---

Update dependency versions to support analyzer 11.x and 12.x.

The specified versions of custom_lint_builder and analyzer_plugin are incompatible with the new analyzer constraint:

• custom_lint_builder: ^0.8.0 constrains analyzer to ^7.5.0 (does not support analyzer 8.0.0+)
• analyzer_plugin: ^0.13.0 constrains analyzer to 7.x versions (does not support analyzer 8.0.0+)

This creates unsatisfiable version constraints that will cause build failures. Update to:

• custom_lint_builder: >=0.8.1 (or higher for broader analyzer support)
• analyzer_plugin: >=0.14.0 (supports analyzer 10.x-12.x)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/freezed_lint/pubspec.yaml` around lines 12 - 14, Update the
dependency constraints in pubspec.yaml to versions compatible with the analyzer
range (>=9.0.0 <13.0.0): change custom_lint_builder from ^0.8.0 to >=0.8.1 (or a
newer non-breaking release) and change analyzer_plugin from ^0.13.0 to >=0.14.0
(or newer) so they support analyzer 11.x/12.x; after updating the
custom_lint_builder and analyzer_plugin entries run pub get and verify the
lockfile to ensure the new versions resolve against the analyzer constraint.

[ThexXTURBOXx]

The issues pointed out by the AI were already there before. They should not matter really.
After my PR is merged, older releases of analyzer will still (additionally) be compatible.

[rrousselGit]

There are many breaking changes involved. This is not enough to upgrade. I'm dealing with this in a separate PR

[ThexXTURBOXx]

Weird - when I tested it, I applied numerous dependency overrides such that I could at least run the dart analyzer on the code and it gave no errors...
But thanks for dealing with this then!