Prepare v2.0.0 release: install from PyPI#50
Conversation
Switch the GitHub Action from source install (uv sync) to PyPI package (pip install good-egg>=2,<3) so consumers get the published artifact. Update self-test workflow to @v2 and stamp the changelog for 2.0.0.
Summary of ChangesHello, 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 prepares the project for its Highlights
Changelog
Ignored Files
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request prepares for the v2.0.0 release by updating the changelog and modifying the GitHub Action to install the good-egg package from PyPI instead of from source. The changes simplify the action's installation logic. My review includes a suggestion to pin the package version in action.yml to improve reproducibility and security.
🥚 Diet Egg: HIGH TrustScore: 84% Score Breakdown
Top Contributions
|
Summary
uv sync) to PyPI package (pip install 'good-egg>=2,<3')@v2Notes
The
v2.0.0tag has already been pushed. Once this PR merges,mainwill match the tag. The release workflow triggered by the tag will publish to PyPI, create the GH release, and set thev2major version tag.