Releases use the manually triggered Publish workflow
on master.
- Update
lib/datadog/statsd/version.rbandCHANGELOG.md, and merge the release changes intomaster. - Confirm that the Ruby Test workflow passes for the release commit.
- Run the Publish workflow, selecting
master, and approve its deployment to therubygems.orgenvironment. - Confirm that the workflow succeeds and the version is available on RubyGems.org and in GitHub releases, with the gem attached to the matching version tag.
The workflow runs the specs, then invokes rubygems/release-gem using the
existing Bundler release task. It builds the gem, creates and pushes its
v<version> tag, publishes it with Sigstore provenance, and waits for it to
be available on RubyGems.org. It then creates a GitHub release for that tag
with generated release notes and attaches the built gem.
Do not create the release tag beforehand.