Skip to main content
Version: v2 (current)

Releases and upgrades for on-prem

TL;DR. PanDev Metrics ships new on-prem builds regularly. Upgrade by swapping image tags in docker-compose.yml (or values.yaml for Helm), then restart. The full per-release changelog with download links lives in Releases → Current release.

Check your current version​

Knowing your current version is the first step before any upgrade conversation.

The running version is exposed by the backend health endpoint:

terminal
curl -s http://<your-server>:9090/actuator/info | jq .build.version

You can also find the version in the web UI footer once you sign in as an admin.

Where to find release notes​

Detailed release notes live in a dedicated documentation section, not in this page.

The detailed per-release changelog, with components versions and download URLs for every plugin, is published in a dedicated section of the documentation:

Each release entry lists:

  • Backend (pandev-metrics) version and Docker tag
  • JetBrains, VS Code, Xcode, Visual Studio plugin versions
  • CLI and browser-extension versions
  • Bug fixes and new features

How to upgrade (Docker Compose)​

A standard Docker Compose upgrade is a four-step swap: back up, edit the tag, pull, restart.

Upgrades are non-destructive — your PostgreSQL data persists across versions. Take a backup first regardless.

  1. Read the release notes for the target version.
  2. Back up PostgreSQL with pg_dump (see backups).
  3. Update the image tag in docker-compose.yml:
docker-compose.yml
services:
  pandev-metrics:
    image: pandevofficial/pandev-metrics:<NEW_VERSION>
    ports:
      - "8080:8080"
      - "9090:9090"
  1. Pull and restart:
terminal
docker compose pull pandev-metrics
docker compose up -d pandev-metrics
  1. Check /actuator/health returns {"status":"UP"} and the version in /actuator/info matches.

Database migrations run automatically on startup.

How to upgrade (Kubernetes / Helm)​

For Helm deployments, change the image tag in values.yaml and run helm upgrade.

  1. Back up PostgreSQL.
  2. Update the image tag in values.yaml:
values.yaml
image:
  tag: <NEW_VERSION>
  1. Apply:
terminal
helm upgrade pandev-metrics ./pandev-metrics -f values.yaml
  1. Watch the rollout:
terminal
kubectl rollout status deployment/pandev-metrics

Backward compatibility​

We aim for forward-only upgrades: install a newer build, the schema migrates in place, and you're done. Downgrades are not supported once migrations have run — restore from a backup if you need to roll back. Plugins (IDE, browser, CLI) are version-tolerant within the same major; update them at your own pace.

FAQ​

Frequently asked questions about on-prem releases and upgrades.

How often do you release on-prem versions?​

PanDev Metrics releases regularly across backend and plugins. Cadence is not fixed — minor versions land every few weeks, patches as needed. Check All releases for the recent rhythm.

Do I need to upgrade plugins together with the backend?​

Not always. Plugins are version-tolerant — older plugins keep working with a newer backend within the same major version. To pick up new features (for example, AI activity tracking in the CLI), update the plugin from the version listed in the release notes.

Can I skip versions when upgrading?​

Yes. Migrations chain forward, so jumping from 4.5.x to 4.7.2 runs every intermediate migration in order. Take a backup first and read the notes for all skipped versions to spot breaking changes.

How do I roll back a bad upgrade?​

Stop the new container, restore the PostgreSQL dump you took before the upgrade, then start the previous image tag. There's no in-place downgrade because schema migrations are forward-only.

Where do I download plugin builds?​

Direct links to JetBrains, VS Code, and Xcode bundles are published with every release entry — see Current release. Host the artifacts on your internal mirror if your developer workstations route IDE traffic through a restricted egress that cannot reach cdn.pandev.io.

Sideways reading for on-prem admins.