Releases
Information about Zipline releases and how to update
Zipline is currently being maintained by me (@diced) and only me. New releases can come out frequently or take a while depending on my schedule. If a new minor/patch release (4.x.x) is not out, you can build from source or use the trunk tag on docker for the latest commit version.
latest
Updated every once in a while, the most frequent updates will be under 4.x.[number] where [number] increments. These may come out every few weeks or so. This is the most stable version of Zipline and is recommended for production use.
Just pull the latest image:
docker pull ghcr.io/diced/zipline:latestFirst switch to the latest tag, for example if the latest tag is 4.0.0, run:
git checkout v4.0.0Then follow the update steps
trunk
Update every time a commit is pushed to the trunk branch. This is the least stable version of Zipline and is not recommended for production use, but is useful if a bug is fixed in the latest commit and you want to use it right away without waiting for the next release.
Just pull the latest image:
docker pull ghcr.io/diced/zipline:trunkThen switch to the trunk tag in your docker-compose file:
image: ghcr.io/diced/zipline:trunkPinning to a specific version
If you want to pin to a specific version or commit for stability reasons, you can do so by using the specific tag for that version or any commit hash.
For example, if you wanted to pin to version v4.3.2, you can use the v4.3.2 tag:
docker pull ghcr.io/diced/zipline:v4.3.2Or if you wanted to pin to a specific commit, you can use the commit hash as the tag:
Note that it must be the short version of the commit hash, which is the first 7 characters of the full commit hash. You can find this in the commit history on GitHub.
docker pull ghcr.io/diced/zipline:abc1234