From 3804b66e7be0108cd35f55c9c059453b367ee449 Mon Sep 17 00:00:00 2001 From: Deepesha Burse <87636253+deepeshaburse@users.noreply.github.com> Date: Tue, 11 Jul 2023 19:31:47 +0530 Subject: [PATCH] Update docs/community/developer_guide.mdx Co-authored-by: Andrew Block Signed-off-by: Deepesha Burse <87636253+deepeshaburse@users.noreply.github.com> --- docs/community/developer_guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/community/developer_guide.mdx b/docs/community/developer_guide.mdx index 0ff8d8b8..cf77175f 100644 --- a/docs/community/developer_guide.mdx +++ b/docs/community/developer_guide.mdx @@ -88,7 +88,7 @@ This section needs a lot of love and automation 🙂 2. If you haven't already, open PR to add your GPG key to the [`KEYS`](https://github.com/oras-project/oras/blob/main/KEYS) file (see file for instructions). 3. Open a release PR to - Build with the latest golang: replace go version of the [binary](https://github.com/oras-project/oras/blob/main/.github/workflows/release-github.yml#L32) and [image](https://github.com/oras-project/oras/blob/main/Dockerfile#L14) to match the latest stable version. - - Update oras version: replace [current stable version](https://github.com/oras-project/oras/blob/main/internal/version/version.go#L20) with upcoming release version. + - Update oras version: replace the [current stable version](https://github.com/oras-project/oras/blob/main/internal/version/version.go#L20) with the upcoming release version. 4. After the release PR got merged, [create an issue](https://github.com/oras-project/oras/issues/new) to call for vote on cutting off a release branch named `release-.` based on the version update commit. 5. Make a fresh clone of the repo after all above steps are completed. Create a new tag for the version prefixed with "v" and push the tag directly to the repo. ```sh