Fix GitHub Actions deprecation and stabilize deployed smoke workflow#14
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this fixes\n- Upgrades Node 20 runtime actions to modern versions (, ).\n- Opts workflows into Node 24 JS action runtime via .\n- Prevents scheduled API smoke runs from hard-failing when is not configured.\n\n## Why\n- Repeated email failures were coming from failing early with no configured target URL.\n- GitHub Actions emitted Node 20 deprecation warnings on .\n\n## Behavior changes\n- still fails if no target URL is provided (intentional explicit run).\n- now skips with a notice if no target URL is configured, reducing noisy failure emails.\n