Harden CI workflows: node bump, runtime version resolution, unbuffered logs - #334
Merged
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.
Three CI hardening changes across the workflows, no source code.
The one checkout action still on Node 16 (in build-docs) is bumped to v4, which clears the deprecation warning repo-wide.
The five fetch workflows had the CS Tools version hardcoded as a tag in each file, so every release meant editing five places. They now resolve the latest release tag at runtime via the releases/latest redirect, with a manual dispatch input still able to override it. Nothing to bump per release.
They also set PYTHONUNBUFFERED so the long extracts stream live logs instead of dumping everything at step end.