Release 1.67.0

[psss]

Notes, contributors, tests

• Review the release notes content and update the text as needed
• Write release notes for any essential changes which were missed
• Verify the rendering locally using make docs or the docs/readthedocs.org:tmt GitHub action check
• Use ./scripts/list-new-contributors to identify new contributors, update docs/overview.rst accordingly
• Commit and push all release notes and contributor changes
• Make sure that the full test coverage has been successfully executed
• Merge the release pull request

Tag, release, downstream

• Make sure you have the release commit: git checkout main && git pull
• Tag the commit with x.y.z, push tags using git push --tags
• Create a new github release based on the tag above
• Mention the most important changes in the release name, do not include version
• Push the “Generate release notes” button to create the content, publish the release
• Check Fedora pull requests and review proposed changes
• Make sure that tests pass and merge individual pull requests

Milestones, container images

• Use the bulk edit in the milestone view to set the milestone for all issues and pull requests included in the sprint
• Close the corresponding release milestone
• Once the non development copr build is completed, run the publish-images workflow to build fresh container image.

[gemini-code-assist]

Summary of Changes

Hello @psss, 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 marks a significant step in the release process for version 1.67.0. It involves organizing and categorizing the release notes by moving them from a temporary 'pending' location to their final, version-specific directory. This action prepares the documentation for the official release, ensuring all relevant changes are correctly attributed to the new version.

Highlights

• Release Preparation: Release notes for version 1.67.0 have been finalized by moving them from the 'pending' directory to the dedicated '1.67.0' release directory.
• Documentation Structure: The file structure for release documentation has been updated to reflect the new version, ensuring that release notes are properly categorized.

Changelog

• docs/releases/1.67.0/3873.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4203.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4379.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4411.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4481.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4482.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4495.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4514.fmf
  • Moved release note from pending to 1.67.0 directory.
• docs/releases/1.67.0/4521.fmf
  • Moved release note from pending to 1.67.0 directory.

Activity

• The pull request description outlines a comprehensive checklist for the release process, indicating this PR is a step within a larger release workflow.
• No specific review comments or discussions have been recorded yet, suggesting this is an initial commit for the release.

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 moves the pending release notes into the docs/releases/1.67.0/ directory as part of the release process for version 1.67.0. The changes consist only of file renames, and there are no code modifications to review. The actions taken are appropriate for preparing a new release.

[psss]

/gemini review

[gemini-code-assist]

Code Review

This pull request prepares for the 1.67.0 release by moving pending release notes to the versioned directory and adding ordering information. The changes are mostly related to documentation. I've noticed that several release notes share the same order value, which could result in an inconsistent order in the final document. I've left a comment with a suggestion to use unique order values for clarity.

[thrix]

LGTM