Migrate to upload-artifact@v4 #49
Merged
Conversation
This file contains 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
tancnle
force-pushed
the
migrate-upload-artifact-v4
branch
from
99ae6a8 to
450a5fe
Compare
Closed
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.
It seems that the build is failing due to artefacts not being found. I think it is due to some compatibility issue between
upload-artifact@v2anddownload-artifact@v4. 🤔In this PR, I have reinstated
upload-artifact@v4and ensured there are no naming conflicts (following the actions/upload-artifact#478 (comment) fromupload-artifactrepo). The artefact links are shown up in the log (source).