arnaucube
/
mirror-to-gitea
mirror of https://github.com/arnaucube/mirror-to-gitea.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 Commits
2 Branches
0 Tags
28 MiB
Tree: 5bde8d1f36
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '5bde8d1f36'
${ noResults }
mirror-to-gitea/vendor/github.com/onsi/ginkgo/RELEASING.md

14 lines
891 B
Raw Normal View History

vendor dependencies
3 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. A Ginkgo release is a tagged git sha and a GitHub release. To cut a release:
  3. 1. Ensure CHANGELOG.md is up to date.
  4. - Use `git log --pretty=format:'- %s [%h]' HEAD...vX.X.X` to list all the commits since the last release
  5. - Categorize the changes into
  6. - Breaking Changes (requires a major version)
  7. - New Features (minor version)
  8. - Fixes (fix version)
  9. - Maintenance (which in general should not be mentioned in `CHANGELOG.md` as they have no user impact)
  10. 1. Update `VERSION` in `config/config.go`
  11. 1. Create a commit with the version number as the commit message (e.g. `v1.3.0`)
  12. 1. Tag the commit with the version number as the tag name (e.g. `v1.3.0`)
  13. 1. Push the commit and tag to GitHub
  14. 1. Create a new [GitHub release](https://help.github.com/articles/creating-releases/) with the version number as the tag (e.g. `v1.3.0`). List the key changes in the release notes.