-
-
Notifications
You must be signed in to change notification settings - Fork 0
build(pip): publish java-api and java-api-stubs to PyPI #5
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
Conversation
Reviewer's GuideAdds automated PyPI publishing for the java-api and java-api-stubs packages upon GitHub releases, and updates the READMEs to point to the new PyPI distributions instead of direct GitHub installs and to reflect current environment details. 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.
Hey there - I've reviewed your changes - here's some feedback:
- In the publish workflow, the step names still say "Upload ignition-api" while the working directories are
java-apiandjava-api-stubs; consider renaming these to match the actual package names to avoid confusion. - For the
pypi-uploadjob, you explicitly pinpython-version: '3.12'only for thejava-api-stubsupload; consider either documenting or aligning the Python version for both uploads to keep the workflow behavior consistent and predictable.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In the publish workflow, the step names still say "Upload ignition-api" while the working directories are `java-api` and `java-api-stubs`; consider renaming these to match the actual package names to avoid confusion.
- For the `pypi-upload` job, you explicitly pin `python-version: '3.12'` only for the `java-api-stubs` upload; consider either documenting or aligning the Python version for both uploads to keep the workflow behavior consistent and predictable.
## Individual Comments
### Comment 1
<location> `.github/workflows/publish.yml:20-21` </location>
<code_context>
+ needs: pr-build
+ runs-on: ubuntu-latest
+ steps:
+ - name: Checkout repo
+ uses: actions/checkout@v6
+
+ - name: Upload ignition-api to PyPI
</code_context>
<issue_to_address>
**🚨 issue (security):** Pin `actions/checkout` to a stable major or SHA instead of `v6`.
`v6` doesn’t exist yet, and major tags can change with breaking updates. Please pin to the current stable major (e.g. `actions/checkout@v4`) or, preferably, to a specific commit SHA to avoid unexpected workflow breakage or behavior changes.
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| - name: Checkout repo | ||
| uses: actions/checkout@v6 |
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.
🚨 issue (security): Pin actions/checkout to a stable major or SHA instead of v6.
v6 doesn’t exist yet, and major tags can change with breaking updates. Please pin to the current stable major (e.g. actions/checkout@v4) or, preferably, to a specific commit SHA to avoid unexpected workflow breakage or behavior changes.
Summary by Sourcery
Publish the java-api and java-api-stubs packages to PyPI on release and update installation instructions accordingly.
CI:
Deployment:
Documentation: