ci: Fix Windows wheel creation#2511
Merged
Merged
Conversation
* Add `actions: read` permission to release workflow. * Configure `download-artifact` action to use `run-id` and `pattern` for downloading wheels from a previous workflow run. * Enable `merge-multiple` for downloading artifacts. * Add `shell: bash` to build step in native release workflow.
This was referenced Aug 25, 2025
chaokunyang
approved these changes
Aug 25, 2025
chaokunyang
pushed a commit
that referenced
this pull request
Aug 25, 2025
## Why? * Wheels were not created on Windows because it does not use bash by default * Once that works, downloading them will fail because `actions/download-artifact` requires the `run-id` to access artifacts from different workflows. ## What does this PR do? * Add `actions: read` permission to release workflow. * Configure `download-artifact` action to use `run-id` and `pattern` for downloading wheels from a previous workflow run. * Enable `merge-multiple` for downloading artifacts. * Add `shell: bash` to build step in native release workflow. ## Related issues #2506
chaokunyang
pushed a commit
to chaokunyang/fory
that referenced
this pull request
Aug 25, 2025
* Wheels were not created on Windows because it does not use bash by default * Once that works, downloading them will fail because `actions/download-artifact` requires the `run-id` to access artifacts from different workflows. * Add `actions: read` permission to release workflow. * Configure `download-artifact` action to use `run-id` and `pattern` for downloading wheels from a previous workflow run. * Enable `merge-multiple` for downloading artifacts. * Add `shell: bash` to build step in native release workflow.
Collaborator
|
The publish still fail: https://github.com/apache/fory/actions/runs/17198889531/job/48785824375 |
chaokunyang
pushed a commit
that referenced
this pull request
Aug 27, 2025
* Wheels were not created on Windows because it does not use bash by default * Once that works, downloading them will fail because `actions/download-artifact` requires the `run-id` to access artifacts from different workflows. * Add `actions: read` permission to release workflow. * Configure `download-artifact` action to use `run-id` and `pattern` for downloading wheels from a previous workflow run. * Enable `merge-multiple` for downloading artifacts. * Add `shell: bash` to build step in native release workflow.
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
2 participants
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.
Why?
actions/download-artifactrequires therun-idto access artifacts from different workflows.What does this PR do?
actions: readpermission to release workflow.download-artifactaction to userun-idandpatternfor downloading wheels from a previous workflow run.merge-multiplefor downloading artifacts.shell: bashto build step in native release workflow.Related issues
#2506