Upgrade the Fencer CLI

Overview

Stay on a supported CLI version. Fencer can reject requests from clients below a minimum version with HTTP 426 Upgrade Required. The CLI then prints:

Your client version (<your version>) is below the minimum required version (<minimum>). Please upgrade.
Upgrade instructions: https://docs.fencer.dev/cli/upgrading/

How it works

Every CLI API request sends X-Fencer-Client: fencer-cli/<semver>. The API compares that semver to its minimum client version. Clients below the minimum cannot call the API until they upgrade. Before raising the minimum, Fencer publishes a sunset_date in the compatibility endpoint at least 90 days in advance.

Check what you are running:

fencer version

The compatibility endpoint (unauthenticated) reports the current minimum:

GET https://app.fencer.dev/api/v1/client-compatibility/

It returns min_client_version, current_client_version, sunset_date (or null), and docs_url.

Upgrade

Re-run the installer for the latest version:

curl -fsSL https://raw.githubusercontent.com/Fencer-Security/cli/main/scripts/install.sh | sh

Pin a version:

curl -fsSL https://raw.githubusercontent.com/Fencer-Security/cli/main/scripts/install.sh | FENCER_CLI_VERSION=0.1.1 sh

Homebrew:

brew update && brew upgrade --cask fencer-security/tap/fencer

Windows: re-run the PowerShell installer from Installation, or replace fencer.exe with the newer zip contents. Debian / RPM: install the newer package from CLI GitHub Releases.

After upgrading, fencer version should show the new semver. Your saved login carries over, so you do not need to log in again.

Releases

Every version is published on the CLI GitHub Releases page, with its archives, packages, SHA256SUMS, signatures, and SBOMs.

Related pages

• Installation
• Troubleshooting