-
Notifications
You must be signed in to change notification settings - Fork 235
Bump to v0.9.2 #1537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to v0.9.2 #1537
Conversation
Signed-off-by: Daniel J Walsh <[email protected]>
Reviewer's GuideThis PR increments the project version from 0.9.1 to 0.9.2 consistently across configuration, source code, and packaging metadata. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @rhatdan, I'm Gemini Code Assist1! 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 updates the project's version number to 0.9.2
. This change is reflected in the Python project metadata, the internal version reporting function, and the RPM spec file, ensuring consistency across the project's build and distribution mechanisms.
Highlights
- Version Bump: Updated the project version from
0.9.1
to0.9.2
.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request updates the project version from 0.9.1 to 0.9.2 across pyproject.toml, ramalama/version.py, and rpm/python-ramalama.spec. Consider centralizing the version string to a single source of truth for future maintainability.
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" | |||
|
|||
[project] | |||
name = "ramalama" | |||
version = "0.9.1" | |||
version = "0.9.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -2,7 +2,7 @@ | |||
|
|||
|
|||
def version(): | |||
return "0.9.1" | |||
return "0.9.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -1,7 +1,7 @@ | |||
%global pypi_name ramalama | |||
%global forgeurl https://github.com/containers/%{pypi_name} | |||
# see ramalama/version.py | |||
%global version0 0.9.1 | |||
%global version0 0.9.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smooge does the rpm spec absolutely need this line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're talking the official distro builds, Packit responds to github release events by creating Fedora PRs that have to be merged by a human. Also, the rpms first go to updates-testing and there's some soak time there before it lands in stable updates.
The human merges of fedora PRs can be timed that way. |
something's weird in the packit job. I don't get why it's trying to fetch the v0.9.2 tag |
Summary by Sourcery
Chores: