Repository navigation
[ci] Use v4 of the artifact actions in the PyPI publish workflow - #13
Merged
Merged
Conversation
GitHub fails any job that uses actions/upload-artifact@v3 or actions/download-artifact@v3 before it starts, so the release v0.4.12 was never built or published: https://github.com/deckhouse/lib-python/actions/runs/38229013146 Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
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
1 participant
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.
The publish workflow of the release v0.4.12 failed before building anything: GitHub rejects jobs that use
actions/upload-artifact@v3andactions/download-artifact@v3(run 38229013146). Both are bumped to v4; the artifact name is used once per run, which v4 requires.actions/setup-python@v4andactions/cache@v3are left as they are: the PR test workflow with them passed on 2026-10-12.After the merge, the release has to be created again on a commit that contains this workflow: the release event runs the workflow file of the tagged commit, and v0.4.12 points at 3fd4ff5, which still has v3.