Upgrade
Upgrading Inspectr is usually a one-liner. Choose the method you originally used to install/run Inspectr.
| Method you use | How upgrades work |
|---|---|
| npx | Always runs the latest version |
| Homebrew | brew upgrade inspectr |
| npm | npm update -g @inspectr/inspectr |
| Binary | Download a newer release and replace the existing binary |
| Docker | Pull the newest image and restart the container |
Upgrade when you run with npx
Section titled “Upgrade when you run with npx”If you run Inspectr via npx, you don’t need to upgrade. Every run downloads and executes the latest published version:
npx @inspectr/inspectr --backend=http://localhost:3000If you want to ensure you’re not using a cached copy, clear the npx cache (optional) and run again.
Upgrade a full installation
Section titled “Upgrade a full installation”Homebrew (macOS)
Section titled “Homebrew (macOS)”Upgrade Inspectr via Homebrew:
brew updatebrew upgrade inspectrVerify:
inspectr --versionUpgrade a global npm install:
npm update -g @inspectr/inspectrIf you want to force a clean reinstall:
npm uninstall -g @inspectr/inspectrnpm install -g @inspectr/inspectrVerify:
inspectr --versionBinary
Section titled “Binary”- Download the newest binary for your platform from GitHub Releases.
- Replace your existing
inspectrbinary with the new one.
If needed, make it executable:
chmod +x ./inspectrVerify:
./inspectr --versionDocker
Section titled “Docker”Pull the latest image:
docker pull ghcr.io/inspectr-hq/inspectr:latestIf you run Inspectr with docker run, stop/remove the old container and start a new one using the updated image:
docker run --rm -p 4004:4004 -p 8080:8080 ghcr.io/inspectr-hq/inspectr:latestDocker Compose
Section titled “Docker Compose”If you use Docker Compose, pull and restart:
docker compose pulldocker compose up -dTo verify the running container is updated:
docker compose psNext step
Section titled “Next step”Explore the configuration options to tailor Inspectr to your workflow.
If something looks off after upgrading, check the release notes on GitHub and compare your current config with the latest CLI docs.