Update workflow with new actions versions and add troubleshooting instructions. #13
Conversation
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
aschlesin
reviewed
Jul 18, 2025
aschlesin
left a comment
aschlesin
left a comment
There was a problem hiding this comment.
This has been the step I needed to successfully push the action thanks!
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.
Hi Patrick, thanks a lot for code, your tutorial and the video.
I've learnt a lot from it!
I'm sharing some of the fixes I made to have the code running as of July 2024.
Running the example gave me a failure related to Node. This was puzzling as I was running a Python script.
GitHub traceback pointed me to a GitHub blog post on actions.
It took me a while to realize the whole GitHub action's infra was changing and all I needed was to use more the more updated pipelines.
At first I was perplexed seeing your action with the old version is still up and running (and logging). Maybe if you set up the action with a valid version that later gets replaced GitHub may update that under the hood?