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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not totally aware of what other changes need to be made. Haven't read the migration process docs yet. But this is causing all use of this Action to fail in CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly for the purposes of fixing this issue might be totally viable to just delete this entire Step. Most folks probably not running in Debug mode. Can add later and adjust params as needed for v4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just forked this Action and unblocked ourselves. Seems this Action does not require any special publish/build process for it to work 🎉
Edit: It does, but the binaries are committed to source and the change to fix this is just in yaml-land, so just forking the Action and pointing to it works just fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That alone should be enough, I think.
Uploaded artifacts are now immutable, so if you try to upload two with the same names in the same pipeline, previously it would have updated the files and now it won't. But this action isn't trying to do that, so I think it should just work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @maschwenk for the PR and you are correct, this should just be a YAML update. I can publish a new package tonight once I am off of work. I may just pull this entirely in the future to minimize dependencies and the fact that it isn't being leveraged a whole lot.