BOT: Dart Dependency Updater

[jpeiffer]

PR created automatically

dependencies:

• pointycastle: 3.9.1 --> 4.0.0

dev_dependencies:

• flutter_lints: 5.0.0 --> 6.0.0
• test: 1.25.12 --> 1.29.0

Error!!!

Resolving dependencies...


Because template_expressions depends on encrypt ^5.0.3 which depends on pointycastle ^3.6.2, pointycastle ^3.6.2 is required.
So, because template_expressions depends on pointycastle ^4.0.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on pointycastle: dart pub add pointycastle:^3.9.1

Summary by CodeRabbit

• Chores
  • Version bumped to 3.3.1+3
  • Automated dependency updates, including pointycastle upgraded to ^4.0.0
  • flutter_lints and test dependencies updated to newer major versions
  • Configuration formatting standardized

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The changes implement a minor version bump to 3.3.1+3 with automated dependency updates. Pointycastle is upgraded from ^3.9.1 to ^4.0.0 (major version), flutter_lints and test are upgraded to newer versions, and all dependency version specifications are reformatted from single quotes to double quotes in pubspec.yaml. A changelog entry documents these updates.

Changes

Cohort / File(s)	Summary
Version & Dependency Updates CHANGELOG.md, pubspec.yaml	Version incremented to 3.3.1+3. Major update: pointycastle upgraded from ^3.9.1 to ^4.0.0. Flutter_lints and test upgraded to newer versions. Standardized string quoting to double quotes throughout pubspec.yaml. Added changelog entry for automated dependency updates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 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 accurately describes the main change: an automated dependency update to Dart packages (pointycastle, flutter_lints, test versions).
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.}

---

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

🤖 Fix all issues with AI agents

In `@pubspec.yaml`:
- Around line 10-23: The pubspec currently lists pointycastle ^4.0.0 which
conflicts with encrypt ^5.0.3 (encrypt depends on pointycastle ^3.6.x); update
the pointycastle dependency in pubspec.yaml to ^3.9.1 so it matches encrypt's
supported range and allows dependency resolution to succeed, leaving the encrypt
entry unchanged.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

encrypt 5.0.3 pub.dev dependencies pointycastle

💡 Result:

Yes — encrypt 5.0.3 uses PointyCastle. The package updated its PointyCastle dependency in the 5.0.x series (5.0.2/5.0.3) to support AES‑GCM / web; typical constraints in that series target PointyCastle 3.6.x (and compatible 3.x) versions. [1][2][3]

Sources:

• encrypt package versions page on pub.dev. [1]
• encrypt 5.0.2 changelog (notes: "Update pointycastle version to support AES‑GCM..."). [2]
• encrypt_next changelog referencing fixes around PointyCastle version parsing (~3.6.2) in 5.0.3 series. [3]

---

🌐 Web query:

pointycastle 4.0.0 pub.dev dependencies

💡 Result:

pointycastle 4.0.0 (pub.dev) dependencies:

• collection
• convert

Minimum Dart SDK: >= 3.2.0. [1]

Sources: pub.dev package page (pointycastle 4.0.0). [1]

References
[1] pub.dev — pointycastle (version 4.0.0) metadata (Dependencies, SDK).

---

🌐 Web query:

encrypt package dart latest version pointycastle support

💡 Result:

Latest encrypt version: 5.0.3 (latest stable on pub.dev). It is a high-level API built on PointyCastle and recent encrypt releases updated its PointyCastle dependency (e.g., pointycastle updates to support AES‑GCM / web in encrypt 5.0.2). Sources: [1],[2].

Sources:
[1] pub.dev - encrypt versions (shows 5.0.3 as latest).
[2] pub.dev - encrypt changelog (notes PointyCastle-related updates, AES‑GCM/web support).

---

Resolve the pointycastle/encrypt version conflict.
encrypt ^5.0.3 depends on pointycastle ^3.6.x, so bumping pointycastle to ^4.0.0 breaks resolution. Downgrade pointycastle to ^3.9.1 to restore compatibility (no newer encrypt version that supports pointycastle ^4 is currently available).

🛠️ Suggested fix

-  pointycastle: "^4.0.0"
+  pointycastle: "^3.9.1"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	convert: "^3.1.2"
	crypto: "^3.0.1"
	encrypt: "^5.0.3"
	fake_async: "^1.3.0"
	intl: ">=0.18.0<1.0.0"
	json_class: "^3.0.1"
	json_path: ">=0.6.3 <1.0.0"
	logging: "^1.3.0"
	meta: "^1.12.0"
	petitparser: "^6.0.1"
	pointycastle: "^4.0.0"
	quiver: "^3.2.2"
	rxdart: "^0.28.0"
	yaon: "^1.1.4+10"
	convert: "^3.1.2"
	crypto: "^3.0.1"
	encrypt: "^5.0.3"
	fake_async: "^1.3.0"
	intl: ">=0.18.0<1.0.0"
	json_class: "^3.0.1"
	json_path: ">=0.6.3 <1.0.0"
	logging: "^1.3.0"
	meta: "^1.12.0"
	petitparser: "^6.0.1"
	pointycastle: "^3.9.1"
	quiver: "^3.2.2"
	rxdart: "^0.28.0"
	yaon: "^1.1.4+10"

🤖 Prompt for AI Agents

In `@pubspec.yaml` around lines 10 - 23, The pubspec currently lists pointycastle
^4.0.0 which conflicts with encrypt ^5.0.3 (encrypt depends on pointycastle
^3.6.x); update the pointycastle dependency in pubspec.yaml to ^3.9.1 so it
matches encrypt's supported range and allows dependency resolution to succeed,
leaving the encrypt entry unchanged.