Package versioning/tagging
Can someone point me toward the versioning of packages in the documentation/source?
Am I correct?
Looking at the container repository for api https://github.com/novuhq/novu/pkgs/container/novu%2Fapi
Tags are: dev, prod, latest, version (eg 0.18.0)
- dev is usually ahead of prod (not always)
- prod looks to be always be latest
- prod always looks to be ahead of the last version tag
- prod is never tagged with a version <-- why??
Also in source, the docker-compose in source is back on 0.17.1.
GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.
1 Reply
Hi @todd7201
Unfortunately there is not a public documentation for version tagging.
We deploy minor version like 0.18.0 after cycle is complete
We don't publish docker images for dev. We publish only for prod.
Main branch is prod and next branch is dev.
There are few manual process involved in version tagging.
Team is working on automating this pipeline