Release Responsible

[usercont-release-bot]

Caution

DO NOT release Packit ≥ 1.0.0 to any of the Fedora releases that already reached the stable by the time of the 1.0.0 release, i.e., Packit CANNOT be released to any Fedora ≤ 41 and EPEL ≤ 9.

Check if there are changes worth releasing for all our RPM-packaged projects:

• ogr
• specfile
• packit
• requre

TODO

Note

Packit is used as an example package below.

• Before creating new releases make sure that pending updates got to stable in Bodhi (if not, ask the team members for karma and wait for it).
• Run Prepare a new release workflow via Run workflow button: choose main branch and type the correct version number for the new release. In a while, you should see the action running and creating a pull request in the repository.
• Review the created PR - you can ask other team members to help you with changelog grammar, if needed. You can check out the PR locally, update it and push it back to the upstream.
  • If the Check release notes required check doesn't run, do a force-push or edit the PR description, that should trigger it.
• Merge the pull request once you're fine with the content (and there are no pending review requests).
• The merge of the PR should trigger an action that creates a draft release in the releases list. Edit the release, make sure the content is correct and then publish the release by clicking Publish release.
• Make sure the package is uploaded to PyPI.

Caution

Do not merge dist-git PRs for Packit project and older releases (F40, F41, EPEL9), they are opened due to this bug.

• Wait a few minutes, check and merge PRs in dist-git created by Packit. You are welcome to use this Claude Code plugin to help you with merging.
  • Check that both services proposed the same set of changes.
  • Merge those created by the stage instance via pull_from_upstream (this will automatically close the Bugzilla from Upstream Release Monitoring)
  • Close those created by the production instance and the production pull_from_upstream.
• If you haven't released all 3 packages, you need to make sure that our sidetag has up to date builds for all our packages. You need to comment /packit-stg koji-tag --all-branches in any dist-git pull request of any package that hasn't been released to satisfy dependencies. This will bring latest builds of each of them in the sidetag. Once all three are updated, it will trigger Koji build of packit and/or Bodhi update: https://dashboard.stg.packit.dev/jobs/koji-tag-requests
  • For example if you are only releasing ogr, you need to comment once in a packit and a specfile dist-git PR.
• Wait a few minutes and verify that RPMs are built in Koji: packit, ogr.
• Wait a bit and verify that updates have been created in Bodhi.
• Celebrate another release 🚀🎉