ceph-csi/vendor/github.com/onsi/ginkgo/v2/RELEASING.md
dependabot[bot] 807f776132 rebase: bump github.com/onsi/ginkgo/v2 from 2.3.1 to 2.4.0
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.3.1 to 2.4.0.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](https://github.com/onsi/ginkgo/compare/v2.3.1...v2.4.0)

---
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2022-10-25 12:57:58 +00:00

858 B

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

  1. Ensure CHANGELOG.md is up to date.
  • Use
    LAST_VERSION=$(git tag --sort=version:refname | tail -n1)
    CHANGES=$(git log --pretty=format:'- %s [%h]' HEAD...$LAST_VERSION)
    echo -e "## NEXT\n\n$CHANGES\n\n### Features\n\n### Fixes\n\n### Maintenance\n\n$(cat CHANGELOG.md)" > CHANGELOG.md
    

to update the changelog

  • 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 VERSION in types/version.go
  2. Commit, push, and release:
git commit -m "vM.m.p"
git push
gh release create "vM.m.p"
git fetch --tags origin master