extern/zrok
1
1
Fork 0
mirror of https://github.com/openziti/zrok.git synced 2025-02-24 14:11:37 +01:00
Code Issues Packages Projects Releases Wiki Activity
059be4c6d0
zrok/RELEASING.md
Kenneth Bingham 059be4c6d0
add stable release promotion workflow
2025-02-13 10:13:53 -05:00

1.7 KiB
Raw Blame History

Releasing zrok

Manual Steps

Note

Each trigger is outlined separately, but some may occur simultaneously, e.g., when a draft release is published as stable rather than first publishing it as a pre-release, or a pre-release is promoted to stable and marked as latest at the same time.

  1. Push a tag to GitHub like v*.*.* to trigger the pre-release workflow. Wait for this workflow to complete before marking the release stable (isPrerelease: false).
    1. Linux packages are uploaded to Artifactory as pre-releases.
    2. Docker images are uploaded to Docker Hub as pre-releases.
    3. A release is drafted in GitHub.
  2. Edit the draft and publish the release as a pre-release (isPrerelease: true).
    1. The one-time GitHub "published" event fires, and binaries are available in GitHub.
  3. Edit the pre-release to mark it as a stable release (isPrerelease: false).
    1. The one-time GitHub "released" event fires.
    2. Linux packages are promoted to "stable" in Artifactory.
    3. Docker images are promoted to :latest in Docker Hub.
    4. Homebrew formulae are built and released.
    5. Python wheels are built and released to PyPi.
    6. Node.js packages are built and released to NPM.
  4. Edit the stable release to mark it as latest.
    1. https://docs.zrok.io/docs/guides/install/ always serves the "latest" stable version via GitHub binary download URLs.

Rolling Back Downstreams

The concepts, tools, and procedures for managing existing downstream artifacts in Artifactory and Docker Hub are identical for zrok and ziti. Here's the RELEASING.md document for ziti.