Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update artifacts GitHub actions to v4 #43

Merged
merged 8 commits into from
Dec 4, 2024
Merged

Conversation

alexrashed
Copy link
Member

@alexrashed alexrashed commented Nov 8, 2024

Motivation

GitHub is currently phasing out support for actions/upload-artifact and actions/download-artifact versions other than the latest major release v4: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Starting December 5, 2024, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact.

This PR updates the the action to v4.

Changes

Update the GitHub artifact action versions to v4 before the burn-down.

@alexrashed alexrashed requested a review from lukqw November 8, 2024 14:58
Copy link

github-actions bot commented Nov 8, 2024

The ephemeral instance for the application preview has been shut down

@alexrashed alexrashed force-pushed the upgrade-artifacts-action branch from d0984a8 to bed5a9f Compare November 19, 2024 16:49
Copy link
Member

@lukqw lukqw left a comment

Choose a reason for hiding this comment

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

Thanks for pro-actively updating our actions 💪
I've added comments that mainly highlight potentially breaking functionality around ephemeral instances

finish/action.yml Show resolved Hide resolved
finish/action.yml Show resolved Hide resolved
ephemeral/startup/action.yml Show resolved Hide resolved
@alexrashed
Copy link
Member Author

Thanks a lot for your comments, @lukqw!
To be honest, I was a bit confused by the flow of the artifacts when using the action.
The only problem which caused me changing the IDs is that it's not allowed anymore with upload-artifacts@v4 to upload two artifacts with the same ID in the same workflow anymore.
Would you mind taking this PR over and just changing it the way you would know it should be?

@lukqw
Copy link
Member

lukqw commented Dec 4, 2024

Thanks a lot for your comments, @lukqw!
To be honest, I was a bit confused by the flow of the artifacts when using the action.
The only problem which caused me changing the IDs is that it's not allowed anymore with upload-artifacts@v4 to upload two artifacts with the same ID in the same workflow anymore.
Would you mind taking this PR over and just changing it the way you would know it should be?

@alexrashed
Understandable that the current flow is confusing, it always takes me some time to understand the multi-artifact setup and flow of artifacts as well.
I didn't know that duplicate IDs are no longer allowed and have updated the PR with that in mind.
I've added new logic which downloads the instance-preview-url artifact, which now makes it available to the workflow further down the line, and have verified it to be working.
I've further added a new assertion step to the ephemeral test suite, which verifies whether a preview comment has been added to the PR - this is the functionality that would have been broken.

@alexrashed
Copy link
Member Author

Awesome! Thanks so much for taking over, fixing the issues, and improving the workflow and assertions!
From my perspective the code also looks great! 💯

@alexrashed alexrashed merged commit aadd2c7 into main Dec 4, 2024
5 checks passed
@alexrashed alexrashed deleted the upgrade-artifacts-action branch December 4, 2024 10:23
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.

2 participants