Fixed early exit when the deployment isn't found #106
Closed
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
Merged
|
Hi @ericallam, Thanks for attempting to resolve the bug! Just a quick update — I’ve already implemented and merged a fix for this issue in another PR. Feel free to take a look and let me know if you have any feedback or questions. I appreciate your efforts on this! |
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.
If a deployment isn't found in the first request, and there are no pagination results, then this action will early return. This fixes the issue by retrying if no deployment is found until one is found, every 5 seconds.
Possible fix for issue #94
You can see an example workflow where this is working here: https://github.com/ericallam/vercel-atomic-deploys/actions/runs/13650544361/job/38157875207