2.8 KiB
Releases
Binaries
Official binaries for OSX, Windows, and Linux can be found on our Github Releases page.
Docker
Pomerium is also distributed as a minimal docker container. You can find Pomerium's images on dockerhub. Pomerium can be pulled in several flavors and architectures.
:vX.Y.Z: which will pull the a specific tagged release.$ docker run pomerium/pomerium:v0.1.0 --version v0.1.0+53bfa4e
-
:latest: which will pull the most recent tagged release.$ docker pull pomerium/pomerium:latest && docker run pomerium/pomerium:latest --version v0.2.0+87e214b
:master: which will pull an image in sync with git's master branch.
Source
If you'd like to run Pomerium on an operating system or architecture not officially released by Pomerium, or simply prefer to compile from source, you can do so by checking out the latest code and compiling as follows.
git clone git@github.com:pomerium/pomerium.git
cd pomerium
make
./bin/pomerium --version
Release Cycle
The current release cycle is aligned on a monthly basis. Pre-1.0.0 we target a MINOR release on or around the first day of each month. We try to hit the targets as closely as possible, while still delivering a quality release.
Versioning
Pomerium uses Semantic Versioning. In practice this means for a given version number vMAJOR.MINOR.PATCH (e.g. v0.1.0):
- MAJOR indicates a incompatible API changes,
- MINOR indicates a new functionality in a backwards-compatible manner, and
- PATCH indicates a backwards-compatible bug fixe.
As Pomerium is still pre-v1.0.0, breaking changes between releases should be expected.
To see difference between releases, please refer to the changelog and upgrading documents.
Versioned Docs
For convenience, we maintain hosted documentation for each tagged release. The format for which is https://{MAJOR}-{MINOR}-{PATCH}.docs.pomerium.io. For example: