Skip to content

release.md

Latest commit

 

History

History
36 lines (30 loc) · 1.36 KB

release.md

File metadata and controls

36 lines (30 loc) · 1.36 KB

Release

This doc covers how to do a release of the tools here.

NOTE: when doing a release make sure that rh-pre-commit always has it's own latest commit that is tagged with it's current version. This keeps pre-commit autoupdate from fetching a weird tag.

You should be able to test it via:

git tag --points-at "$(git describe FETCH_HEAD --tag --abbrev=0)"

Steps

  1. Make sure the versions are updated
  2. Run make specfile and commit the changes
  3. Draft the changelog entry
  4. Review and test code
    1. Make sure there are no issues
    2. Make sure docs are taken into account
    3. Make sure GitLab issues have been addressed
  5. Merge into main
  6. Checkout main and pull latest
  7. Run the following replacing the version
    1. git commit --allow-empty -m "rh-gitleaks-VERSION"
    2. git tag rh-gitleaks-VERSION
    3. git commit --allow-empty -m "rh-pre-commit-VERSION"
    4. git tag rh-pre-commit-VERSION
    5. git push && git push --tags
  8. Build RPMs in COPR
  9. Do a quickstart.sh install again to do one last round of testing and verify versions
  10. Publish the changelog
  11. Update the .pre-commit-config.yaml through a pre-commit autoupdate and merge in the changes
  12. Close out any now-resolved GitLab issues