Skip to content

feat: update wheelhouse artifacts names#1112

Open
jorgepiloto wants to merge 9 commits intomainfrom
feat/unify-artifact-names
Open

feat: update wheelhouse artifacts names#1112
jorgepiloto wants to merge 9 commits intomainfrom
feat/unify-artifact-names

Conversation

@jorgepiloto
Copy link
Member

There is no convention for wheelhouses as opposite to Python distribution artifacts. Knowing that these last impose underscores in the name of the projects but use hyphens for separating metadata, I decided to follow the same approach with the wheelhouse. Fixes #681.

@jorgepiloto jorgepiloto requested a review from a team as a code owner January 14, 2026 14:44
@github-actions github-actions bot added the enhancement General improvements to existing features label Jan 14, 2026
@jorgepiloto jorgepiloto force-pushed the feat/unify-artifact-names branch from d10e214 to 83554a6 Compare January 14, 2026 14:48
Copy link
Contributor

@SMoraisAnsys SMoraisAnsys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jorgepiloto I think you only have to change the file name to have your changes working

Regarding the changes, I don't have a strong opinion and am fine with the proposed changes.

Copy link
Member

@RobPasMue RobPasMue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also check that other actions like the GitHub release are not impacted by this change. I'm not sure what naming convention it was expecting for wheelhouse artifacts.

@jorgepiloto
Copy link
Member Author

We should also check that other actions like the GitHub release are not impacted by this change. I'm not sure what naming convention it was expecting for wheelhouse artifacts.

Good point. So far, I checked the release ones. They use a glob pattern like *-wheelhouse-*, so we should be safe.

Copy link
Contributor

@moe-ad moe-ad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shell substitutions will not work in this situation. It should be interpolated directly. This needs to be repeated for other cases as well.

Co-authored-by: Maxime Rey <87315832+MaxJPRey@users.noreply.github.com>
Co-authored-by: Muhammed Adedigba <68085496+moe-ad@users.noreply.github.com>
@moe-ad
Copy link
Contributor

moe-ad commented Mar 18, 2026

@SMoraisAnsys @RobPasMue
I finalized things here, can you give it a last look before it gets merged?

Copy link
Member

@RobPasMue RobPasMue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me I think - let's see if it has some unexpected impact in other places we are not aware currently

Copy link
Contributor

@SMoraisAnsys SMoraisAnsys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I checked the repo and couldn't find a place where those changes could be a problem.

Copy link
Contributor

@SMoraisAnsys SMoraisAnsys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@moe-ad Could you perform a test from an external repo to ensure that nothing is missed ? This would require to point to the PR's branch. Still thinking that this is fine but calling a request for changes to ensure that someone does take the time to test before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement General improvements to existing features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unify artifacts file names

6 participants