From e57eb4c4745e0363c22d1bb7d4993dd838460b08 Mon Sep 17 00:00:00 2001 From: Yuwen Ma Date: Fri, 7 Apr 2023 17:27:52 -0700 Subject: [PATCH] Update RELEASING.md --- RELEASING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index 7e2e41803..21bd0b7c7 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -12,8 +12,12 @@ kpt-functions-catalog repo. `{funtion-name} {semver}`. The release notes for this function should be in the body. 1. Click `Publish release` button. +1. Verify the new functions is released in gcr.io/kpt-fn/{funtion-name}/{semver} 1. Send an announcement email in the [kpt users google group]. +Note: For most functions, you can ignore the GitHub action "Run the CD script after tags that look like versions". It is only for functions that have +KO build and release setup. Currently only three functions uses ko to release: `bind`, `ensure-name-substring`, `set-gcp-resource-ids`. + ## Updating function docs After creating a release, the docs for the function should be updated to reflect