Release 1.54.0

[psss]

Follow the steps below to create a new major or minor release:

• Update overview.rst with new contributors since the last release
• Review the release notes in releases.rst, update as needed
• Add a Release x.y.z commit, empty if needed: git commit --allow-empty -m "Release x.y.z"
• Create a pull request with the commit, ensure tests pass, merge it
• Move the fedora branch to point to the new release
• Tag the commit with x.y.z, push tags git push --tags

Create a new github release based on the tag above

• Mention the most important changes in the name, do not include version
• Use ; as a delimiter, when multiple items are mentioned in the name
• Push the “Generate release notes” button to create the content
• Prepend the “See the release notes for the list of interesting changes.” line
• Publish the release, check Fedora pull requests, make sure tests pass and merge

Finally, if everything went well

• Close the corresponding release milestone
• Once the non development copr build is completed, run the publish-images workflow to build fresh container image.

Handle manually what did not went well

• If the automation triggered by publishing the new github release was not successful, publish the fresh code to the pypi repository manually using make wheel && make upload
• If there was a problem with creating Fedora pull requests, you can trigger them manually using /packit propose-downstream in any open issue.

[psss]

/packit build

[psss]

Full test coverage executed in #3899, merging.