[mambax7]

#639 moved JetBrains/qodana-action to v2026.2.2, but qodana.yaml still pins the qodana-php:2025.3 image. Qodana rejects a linter from a different release than its CLI (this is what failed CI before #642). The scan is currently skipped because QODANA_TOKEN is not set, so CI is green either way. Without this change, Qodana would start failing as soon as a token is added.

Summary by Sourcery

Bug Fixes:

• Align the Qodana PHP linter image with the 2026.2 CLI release to prevent release-version mismatches when authenticated scans run.

Summary by CodeRabbit

• Chores
  • Updated the project’s code quality analysis tooling. No user-facing changes are included.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: XOOPS/XoopsCore26/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Essentials
• Run ID: 4426ceec-41a9-4c19-9ee1-2bf988965d46

📥 Commits

Reviewing files that changed from the base of the PR and between 41be5b3 and 5004ddf.

📒 Files selected for processing (1)

• qodana.yaml

Included review availability: This review used your included allowance. Your plan provides up to 5 included reviews per hour; 1 remain after this review.

---

Walkthrough

The Qodana configuration changes its PHP image tag from 2025.3 to 2026.2.

Changes

Qodana image update

Layer / File(s)	Summary
Update Qodana PHP image tag qodana.yaml	The configured image tag changes from 2025.3 to 2026.2.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 5004d

The scan uses a published PHP linter image matching the configured Qodana CLI release, so this change presents no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating the Qodana linter image to match the 2026.2 CLI.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

[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

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.41%. Comparing base (befbbd0) to head (5004ddf).
⚠️ Report is 7 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #643   +/-   ##
=========================================
  Coverage     49.40%   49.41%           
  Complexity     4689     4689           
=========================================
  Files           269      269           
  Lines         13242    13242           
=========================================
+ Hits           6542     6543    +1     
+ Misses         6700     6699    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

🟢 Approval recommended

The image version now correctly matches the workflow’s Qodana CLI release.

0 open findings

What changed in this PR

Aligns the Qodana PHP linter image with the 2026.2 CLI used by the GitHub Actions workflow.

Changes:

• Updates the Qodana PHP image from 2025.3 to 2026.2.

File	Description
qodana.yaml	Pins the matching 2026.2 Qodana PHP image.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Qodana PHP linter image to 2026.2 so it matches the CLI version introduced by the action upgrade, preventing token-enabled scans from failing due to a release mismatch.

File-Level Changes

Change	Details	Files
Align the Qodana PHP linter image with the 2026.2 CLI used by the GitHub Action.	Update the pinned image from the 2025.3 release to 2026.2. Keep the existing Qodana version, recommended profile, and configuration structure unchanged.	qodana.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook