Technical: upgrade farao parent version to resolve CVE issues

[kahyami]

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX' and skip the rest

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

Summary by CodeRabbit

• Chores
  • Updated parent project dependency to version 1.14.0
  • Updated FARAO dependencies to version 1.46.0

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

[coderabbitai]

Walkthrough

Parent Maven version bumped from 1.13.0 to 1.14.0, and farao.dependencies.version property updated from 1.44.1 to 1.46.0 in pom.xml.

Changes

Cohort / File(s)	Summary
Maven configuration pom.xml	Updated parent version to 1.14.0 and farao.dependencies.version to 1.46.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Straightforward dependency version bumps with no logic or structural changes.

Possibly related PRs

• Upgrade farao dependencies version to v1.41.0 #86: Updates the same farao.dependencies.version property in pom.xml.
• upgrade farao-dependencies version #84: Modifies farao.dependencies.version to bump farao dependencies.
• Upgrade farao-dependencies version to v1.43.0 #91: Updates farao.dependencies.version to a different target version.

Poem

🐰 Hop, hop, the versions rise!
New parent blooms before our eyes,
Dependencies dance to version 1.46,
A minor bump to fix and flex,
Small pom.xml adjustments bring such glee! ✨

Pre-merge checks and finishing touches

✅ 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 clearly summarizes the main change: upgrading the farao parent version to resolve CVE issues. This accurately reflects the primary modification in the changeset (parent version 1.13.0 → 1.14.0).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch technical_upgrade

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 045e61d and 9fc44fe.

📒 Files selected for processing (1)

• pom.xml (2 hunks)

🔇 Additional comments (2)

pom.xml (2)

10-10: Verify the parent version upgrade and CVEs resolved.

The parent version bump from 1.13.0 to 1.14.0 should be validated in the farao-parent release notes.

Please verify:

1. The version exists and is valid
2. Which specific CVEs this version resolves
3. Whether there are any breaking changes

---

52-52: Verify farao-dependencies version 1.46.0 and CVE fixes through internal release notes.

The farao-dependencies version bump from 1.44.1 to 1.46.0 skips version 1.45.x. Please verify through FARAO project documentation or release notes:

1. The version is available and compatible
2. Which CVEs are addressed by this upgrade
3. Any breaking changes between 1.45.0 and 1.46.0

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

pom.xml (1)

48-82: Upgrade logback-classic beyond 1.5.12 to address CVE-2024-12798.

logback-classic 1.5.12 has a CVE-2024-12798 vulnerability that allows arbitrary code execution through the JaninoEventEvaluator by compromising a logback configuration file or injecting an environment variable. Version 1.5.13 removed JaninoEventEvaluator to mitigate this vulnerability. Upgrade logback-classic to 1.5.13 or later.

Also verify tests pass with the updated versions.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 045e61d and 9fc44fe.

📒 Files selected for processing (1)

• pom.xml (2 hunks)

🔇 Additional comments (2)

pom.xml (2)

10-10: Verify the parent version upgrade and CVEs resolved.

The parent version bump from 1.13.0 to 1.14.0 should be validated in the farao-parent release notes.

Please verify:

1. The version exists and is valid
2. Which specific CVEs this version resolves
3. Whether there are any breaking changes

---

52-52: Verify farao-dependencies version 1.46.0 and CVE fixes through internal release notes.

The farao-dependencies version bump from 1.44.1 to 1.46.0 skips version 1.45.x. Please verify through FARAO project documentation or release notes:

1. The version is available and compatible
2. Which CVEs are addressed by this upgrade
3. Any breaking changes between 1.45.0 and 1.46.0