Skip to content

Update handling of artifacts in python-package.yml#649

Merged
wbarnha merged 1 commit into
masterfrom
update-artifact-cicd
Nov 21, 2024
Merged

Update handling of artifacts in python-package.yml#649
wbarnha merged 1 commit into
masterfrom
update-artifact-cicd

Conversation

@wbarnha

@wbarnha wbarnha commented Nov 21, 2024

Copy link
Copy Markdown
Member

This will allow us to start making releases again.

This will allow us to start making releases again.
@codecov

codecov Bot commented Nov 21, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.09%. Comparing base (8eb5cd7) to head (8d30de3).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #649   +/-   ##
=======================================
  Coverage   94.09%   94.09%           
=======================================
  Files         102      102           
  Lines       11100    11100           
  Branches     1328     1328           
=======================================
  Hits        10444    10444           
  Misses        557      557           
  Partials       99       99           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@wbarnha
wbarnha merged commit af0ed79 into master Nov 21, 2024
@wbarnha
wbarnha deleted the update-artifact-cicd branch November 21, 2024 20:44
wbarnha added a commit that referenced this pull request Jul 17, 2026
#649 bumped upload/download-artifact from v3 to v4 but kept the v3
pattern where every build_wheels matrix leg (and the sdist) uploaded
under a shared artifact name and the publish job downloaded a single
name. v3 merged same-named uploads; v4 does not -- each upload is its
own immutable artifact and uploading the same name again fails. So the
three matrix legs collide on 'wheel-artifacts', and the wheel download
used pattern '*artifact*' with no path (landing outside dist/, which is
what gh-action-pypi-publish publishes from). The last release (v0.11.3)
predates #649 and used v3, so this is latent -- the next release would
fail to publish or ship incomplete artifacts.

Give each uploader a unique name (cibw-wheels-<os>, cibw-sdist), collect
them all in the publish job with pattern: cibw-* + merge-multiple into
dist/, add skip-existing so re-runs can backfill, and if-no-files-found:
error so an empty build fails loudly instead of silently publishing
nothing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant