Versions

These docs describe version 2.0.0 of Hardcharger™, its first general release. Every example runs against a server of that version in CI.

How versions work

• Hardcharger follows semantic versioning: a major version may change options or behavior, a minor version adds to them, and a patch version only fixes things.
• A release candidate (2.0.0-rc.1) comes before its release. It is a pre-release: its image is tagged with its version (:2.0.0-rc.1), never :latest.
• The server, the hardcharger CLI and the container image share one version. The drivers (Python, Go, JDBC, JavaScript) are versioned on their own and speak Warp SQL, whose protocol version the server reports at GET /warp (protocol_versions).
• HARDCHARGER_VERSION() and hardcharger-server --version report the server’s version.
• Upgrading covers moving between versions and rolling back.

What changed in each release

The release notes list every change, release by release.

Older and newer versions

Each release’s docs will be kept at their own path, next to latest, with a version picker in the header.