From 2b0e8ef726bc401335727e8585aa0554bc23f3ee Mon Sep 17 00:00:00 2001 From: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com> Date: Wed, 3 Jul 2024 14:57:06 -0700 Subject: [PATCH] Document how to release flytectl (#5537) Signed-off-by: Eduardo Apolinario Co-authored-by: Eduardo Apolinario --- flytectl/RELEASE.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 flytectl/RELEASE.md diff --git a/flytectl/RELEASE.md b/flytectl/RELEASE.md new file mode 100644 index 0000000000..646f7465a6 --- /dev/null +++ b/flytectl/RELEASE.md @@ -0,0 +1,5 @@ +# Release Process + +Flytectl releases map to git tags with the prefix `flytectl/` followed by a semver string, e.g. [flytectl/v0.9.0](https://github.com/flyteorg/flyte/releases/tag/flytectl%2Fv0.9.0). + +To release a new version of flytectl push a new git tag in the format described above. This will kick off a <[github workflow](https://github.com/flyteorg/flyte/blob/master/.github/workflows/flytectl-release.yml) responsible for releasing this new version. Note how the git tag has to be formatted a certain way for the workflow to run.