Skip to content

RELEASING.md

Latest commit

 

History

History
29 lines (22 loc) · 1.23 KB

RELEASING.md

File metadata and controls

29 lines (22 loc) · 1.23 KB

Releasing wild

  • Manually trigger the release workflow to verify that it still works.
  • Run git cliff {previous version}...
  • Copy output into CHANGELOG.md and edit as necessary.
  • The header for the release must be just the version number that is going to be released.
    • If in doubt, run the awk command from release.yml
  • Change version in workspace Cargo.toml
  • Search for version = "{old version}" for other places to update.
  • Ensure that the above changes are merged into the main repository.
  • Sync local repo to upstream main. i.e. no uncommitted changes.
  • Run cargo publish for each package.
  • Trigger the github release action by pushing a tag for the version number.
git tag 0.6.0 # Where "0.6.0" is the number in Cargo.toml 
git push origin refs/tags/0.6.0

That should trigger the release.yml workflow in GitHub. You can follow its progress in the Actions tab in GitHub.

When complete, it should create the release in Releases.

Maintainers can then edit the release notes associated with the release.

If everything looks good, publish the release.

Update wild-action.