Git artifact name update#264
Merged
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b4f5bac. Configure here.
chethan-rfai
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Changes
Note
Medium Risk
Changes how production packages reach PyPI (trusted publishing vs API token) and artifact naming; misconfiguration could block releases or publish the wrong build.
Overview
Release and manual PyPI workflows now use versioned wheel artifact names (
rapidfireai-<version>-wheel-<ref>) and uploaddist/*with stricterif-no-files-foundhandling; the manual workflow renames the upload step to match.The release-on-publish workflow (
deploy-pypi.yml) is refactored to match manual deploy: build job outputs version frompyproject.toml, runstwine check, uploads artifacts (90-day retention), then a separatepublish-to-pypijob downloads the same artifact name and publishes viapypa/gh-action-pypi-publishwith thepypienvironment and OIDC (id-token: write) instead of inlinetwine uploadandPYPI_API_TOKEN_SUPPORT_DEV.Reviewed by Cursor Bugbot for commit 50bf48c. Bugbot is set up for automated code reviews on this repo. Configure here.