Qodana 2026.2 Help

Upgrading Qodana

Upgrading Qodana to actual versions is a necessary step. For example, new features published in Qodana Cloud can be incompatible with older versions of Qodana. The current Qodana version is 2026.2.

This section explains how you can upgrade Qodana to the latest version depending on the available deployment options.

Qodana CLI

Depending on how you deployed Qodana CLI on your machine, run one of the following commands:

Upgrade with Homebrew:

brew upgrade qodana

Upgrade Qodana CLI to a specific version using our installer:

curl -fsSL https://jb.gg/qodana-cli/install | bash -s -- v2026.2.1

On Linux, you can also upgrade Qodana using Go:

go install github.com/JetBrains/qodana-cli@latest

Upgrade with Windows Package Manager:

winget upgrade -e --id JetBrains.QodanaCLI

Upgrade with Chocolatey:

choco upgrade qodana

Upgrade with Scoop:

scoop update qodana

CI/CD platforms

Depending on a CI/CD platform used, you should keep upgraded either the Docker image version or the Qodana application version while configuring, see the snippets below.

The task: QodanaScan@2026 line configures the major version of the Qodana task and automatically employs the newest minor version. Use this line to upgrade Qodana to the newest major version:

trigger: - main   pool: vmImage: ubuntu-latest   steps: - checkout: self persistCredentials: true - task: Cache@2 inputs: key: '"$(Build.Repository.Name)" | "$(Build.SourceBranchName)" | "$(Build.SourceVersion)"' path: '$(Agent.TempDirectory)/qodana/cache' restoreKeys: | "$(Build.Repository.Name)" | "$(Build.SourceBranchName)" "$(Build.Repository.Name)" - task: QodanaScan@2026 inputs: uploadResult: true env: QODANA_TOKEN: $(QODANA_TOKEN)

The image: jetbrains/qodana-<image>:2026.2 line configures the Docker image used for Qodana and specifies its version:

image: atlassian/default-image:4 pipelines: branches: main: - step: name: Qodana caches: - qodana image: jetbrains/qodana-<image>:2026.2 script: - export QODANA_TOKEN=$QODANA_TOKEN - qodana --results-dir=$BITBUCKET_CLONE_DIR/.qodana --report-dir=$BITBUCKET_CLONE_DIR/.qodana/report --cache-dir=$HOME/.qodana/cache artifacts: - .qodana/report definitions: caches: qodana: .qodana/cache

The qodana: jetbrains/qodana@2026.2 line configures the version of the used CircleCI Qodana orb:

version: 2.1 orbs: qodana: jetbrains/qodana@2026.2 jobs: code-quality: machine: image: 'ubuntu-2004:current' environment: $QODANA_TOKEN steps: - checkout - qodana/scan workflows: main: jobs: - code-quality: context: qodana

The uses: JetBrains/qodana-action@v2026.2 line configures the version of the employed Qodana Scan GitHub action:

name: Qodana on: workflow_dispatch: pull_request: push: branches: # Specify your branches here - main # The 'main' branch - master # The 'master' branch - 'releases/*' # The release branches   jobs: qodana: runs-on: ubuntu-latest permissions: contents: write pull-requests: write checks: write steps: - uses: actions/checkout@v3 with: ref: ${{ github.event.pull_request.head.sha }} # to check out the actual pull request commit, not the merge commit fetch-depth: 0 # a full history is required for pull request analysis - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2026.2 with: args: | --linter <qodana-linter> --within-docker false env: QODANA_TOKEN: ${{ secrets.QODANA_TOKEN }}

Configure the newest version of the Qodana Scan GitLab Pipeline component and the Docker image as shown below:

include: - component: $CI_SERVER_FQDN/qodana/qodana/qodana-gitlab-ci@v2026.2 inputs: image: jetbrains/qodana-<image>:2026.2

The component and Docker image versions should be identical so that Qodana can operate correctly.

The image 'jetbrains/qodana-<image>:2026.2' line configures the Docker image used for Qodana and specifies its version:

pipeline { environment { QODANA_TOKEN=credentials('qodana-token') } agent { docker { args ''' -v "${WORKSPACE}":/data/project --entrypoint="" ''' image 'jetbrains/qodana-<image>:2026.2' } } stages { stage('Qodana') { steps { sh '''qodana''' } } } }

On the Qodana runner configuration page, click Show advanced options and make sure that Version is set to Latest.

14 September 2026