Files
podman/vendor/github.com/onsi/gomega/RELEASING.md
Valentin Rothberg 9ac0ebb079 Cirrus: add vendor_check_task
* Make sure that all vendored dependencies are in sync with the code and
  the vendor.conf by running `make vendor` with a follow-up status check
  of the git tree.

* Vendor ginkgo and gomega to include the test dependencies.

Signed-off-by: Chris Evic <cevich@redhat.com>
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
2019-02-06 11:14:06 +01:00

776 B

A Gomega release is a tagged sha and a GitHub release. To cut a release:

  1. Ensure CHANGELOG.md is up to date.
  • Use git log --pretty=format:'- %s [%h]' HEAD...vX.X.X to list all the commits since the last release
  • Categorize the changes into
    • Breaking Changes (requires a major version)
    • New Features (minor version)
    • Fixes (fix version)
    • Maintenance (which in general should not be mentioned in CHANGELOG.md as they have no user impact)
  1. Update GOMEGA_VERSION in gomega_dsl.go
  2. Push a commit with the version number as the commit message (e.g. v1.3.0)
  3. Create a new GitHub release with the version number as the tag (e.g. v1.3.0). List the key changes in the release notes.