build(deps): bump JetBrains/qodana-action from 2026.1.3 to 2026.2.0 - #111
build(deps): bump JetBrains/qodana-action from 2026.1.3 to 2026.2.0#111dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [JetBrains/qodana-action](https://github.com/jetbrains/qodana-action) from 2026.1.3 to 2026.2.0. - [Release notes](https://github.com/jetbrains/qodana-action/releases) - [Commits](JetBrains/qodana-action@v2026.1.3...v2026.2.0) --- updated-dependencies: - dependency-name: JetBrains/qodana-action dependency-version: 2026.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
| - name: 🔍 Qodana Scan | ||
| id: qodana | ||
| uses: JetBrains/qodana-action@v2026.1.3 | ||
| uses: JetBrains/qodana-action@v2026.2.0 |
There was a problem hiding this comment.
🔍 Cache keys still reference Qodana 2025.3 while action moves to 2026.2.0
The Qodana step's primary-cache-key/additional-cache-key (.github/workflows/code-quality.yml:38-39) are hardcoded to qodana-2025.3-..., which no longer matches the action version being used (now 2026.2.0). This is pre-existing (the keys were already stale for 2026.1.3), but the bump makes it more misleading: caches produced by different Qodana major versions share the same key, which can lead to reusing incompatible cache contents. Consider parameterizing the version in the cache key.
Was this helpful? React with 👍 or 👎 to provide feedback.
| - name: 🔍 Qodana Scan | ||
| id: qodana | ||
| uses: JetBrains/qodana-action@v2026.1.3 | ||
| uses: JetBrains/qodana-action@v2026.2.0 |
There was a problem hiding this comment.
🔍 New action release changes exit-code propagation semantics
The 2026.2.0 release notes include "QD-13746 pass Qodana exit code in action" and "QD-15410 check that in case of pr-mode: true the repository checked out to source branch". The step uses continue-on-error: true (.github/workflows/code-quality.yml:31) so a newly propagated non-zero exit (with --fail-threshold 0) won't fail the job, but steps.qodana.outcome semantics may change for any downstream consumers. The checkout step also pins ref: ${{ github.event.pull_request.head.sha }} rather than the source branch, which could interact with the new pr-mode branch check if pr-mode is ever enabled.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Qodana Community for .NET10 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.2.0
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|



Bumps JetBrains/qodana-action from 2026.1.3 to 2026.2.0.
Release notes
Sourced from JetBrains/qodana-action's releases.
Commits
b588768QD-15622 ⬆️ Updateqodanatov2026.2.0(#611)d37471b🐛 QD-14507 Add title parameter to gh release create command (#593)8069c0fQD-15420 Warn about sanity problems in the summary posted in the pull request...e11337fQD-15410 check that in case of pr-mode: true the repository checked out to so...1f6f293QD-15472 bump tar dependencyf28920a:docs: Update qodana-maven-plugin version to 2026.1.3cf5541eQD-12982 skip pull in action if arg is specified97d17d6QD-13746 pass Qodana exit code in actionf4341f6QD-14362 bump color able axios version to 1.15.269c00ce🐛 Fix azure release workflow husky error (#604)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)