Skip to content

Commit

Permalink
Update docs/community/developer_guide.mdx
Browse files Browse the repository at this point in the history
Co-authored-by: Andrew Block <andy.block@gmail.com>
Signed-off-by: Deepesha Burse <87636253+deepeshaburse@users.noreply.github.com>
  • Loading branch information
deepeshaburse and sabre1041 authored Jul 11, 2023
1 parent 3804b66 commit 20711ac
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/community/developer_guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ This section needs a lot of love and automation 🙂
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 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-<major>.<minor>` based on the version update commit.
4. After the release PR gets merged, [create an issue](https://github.com/oras-project/oras/issues/new) to call for a vote cutting off a release branch named `release-<major>.<minor>` 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
version=1.0.0
Expand Down

0 comments on commit 20711ac

Please sign in to comment.