Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 1.26 KB

RELEASE.md

File metadata and controls

34 lines (22 loc) · 1.26 KB
Raw

Release

This document describes the steps to release a new version of the wit-bindgen-go CLI.

1. Prerequisites

If package cm has changed, make the neccessary updates to cm/CHANGELOG.md and create a new release for go.bytecodealliance.org/cm. Then update the dependency in this module by running:

go get -u go.bytecodealliance.org/cm@latest

Commit those changes prior to tagging a new release of this module.

2. Update CHANGELOG.md

  1. Add the latest changes to CHANGELOG.md.
  2. Rename the Unreleased section to reflect the new version number.
    1. Update the links to new version tag in the footer of CHANGELOG.md
  3. Add today’s date (YYYY-MM-DD) after an em dash (—).
  4. Submit a GitHub Pull Request with these updates.

3. Create a new release

Once the PR is merged, tag the new version in Git and push the tag to GitHub.

For example, to tag version v0.3.0:

git tag v0.3.0
git push origin v0.3.0

After the tag is pushed, GitHub Actions will automatically create a new release with the content of the CHANGELOG.md file.