We follow the semantic versioning, numbered with
Docker Image Tag Explained¶
||the last Sunday release, contains the bare minimum of to run Jina framework.|
||(previous) Sunday release.|
||the development version corresponds to the latest master, it extends
||shortcut alias to the last
Which Version to Use?¶
latest, if you want to use barebone Jina framework and extend it with your own modules/plugins.
devel, if you want to use Dashboard to get more insights about the logs and flows.
Docker Image Size of Different Versions¶
The last update image is
Every successful merge into the master triggers a development release. It will:
update the Docker image with tag
update jina-ai/docs tag
Note, commits started with
chore are exceptions and will not trigger the events above. Right now these commits are:
chore(docs): update TOC
chore(version): bumping master version
Sunday Auto Release¶
On every Sunday 23pm, a patch release is scheduled:
tag the master as
vx.y.zand push to the repo;
create a new tag
x.y.zdocker image, with tag
x.y.zpackage on PyPI;
bump the master to
x.y.(z+1)and commit a
The current master version should always be one version ahead of
git tag -l | sort -V | tail -n1.
Every midnight at 0:00, the docker image tagged with
x.y.z-devel will be rebuilt on all platforms, include: linux/amd64, linux/arm64, linux/ppc64le, linux/386, linux/arm/v7, linux/arm/v6.