Release 0.61.0

[usercont-release-bot]

Update the changelog and the specfile for release 0.61.0.

[gemini-code-assist]

Summary of Changes

Hello @usercont-release-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request prepares for the release of version 0.61.0 by updating the project's version number and changelog. The primary new feature introduced in this version is the expanded support for Forgejo, specifically for issues, comments, and comment reactions, enhancing the ogr library's compatibility with this git forge.

Highlights

• Version Update: The project version has been updated from 0.60.1 to 0.61.0 across relevant configuration files.
• Changelog Entry: A new entry for version 0.61.0 has been added to CHANGELOG.md, highlighting the new support for Forgejo issues, comments, and comment reactions.
• Spec File Update: The Fedora spec file (fedora/python-ogr.spec) has been updated to reflect the new version and includes a corresponding changelog entry.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• CHANGELOG.md
  • Added a new section for version 0.61.0 at the top of the file.
  • Included a new entry detailing Forgejo support for issues, comments, and comment reactions.
• fedora/python-ogr.spec
  • Updated the Version field from 0.60.1 to 0.61.0.
  • Added a new entry to the %changelog section for version 0.61.0-1, indicating a new upstream release.

Activity

• The pull request was created by usercont-release-bot to automate the release process.
• No human comments or reviews have been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request prepares for the 0.61.0 release by updating the CHANGELOG.md and fedora/python-ogr.spec files. The version number is correctly bumped to 0.61.0, and the changelogs are updated to reflect the new features included in this release. The changes are consistent and look correct for a release.

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/24f5499ea3364690a472f1c121bbe19e

✔️ pre-commit SUCCESS in 3m 25s
✔️ ogr-tests-pip-deps SUCCESS in 11m 19s

[centosinfra-prod-github-app]

Build succeeded (gate pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/c5152c152e5e448dabcbaed825968f72

✔️ pre-commit SUCCESS in 3m 18s

[centosinfra-prod-github-app]

Pull request merge failed: Required status checks "rpm-build:fedora-42-x86_64" and "testing-farm:fedora-42-x86_64" were not set by the expected GitHub apps.

[packit-as-a-service-stg]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {10: {'packages': defaultdict(<class 'dict'>, {'python-ogr': {'value': {'bodhi_extra_params': ['Unknown field.']}}})}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command config validate or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {10: {'packages': defaultdict(<class 'dict'>, {'python-ogr': {'value': {'bodhi_extra_params': ['Unknown field.']}}})}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command config validate or our pre-commit hooks for validation of the configuration.

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/8cf476be91fc4bf29a2ddf212f719e9f

✔️ pre-commit SUCCESS in 3m 21s
✔️ ogr-tests-pip-deps SUCCESS in 11m 16s