Update CI actions to node24#89
Merged
Merged
Conversation
Bump the GitHub Actions and bonsai-rx composites in the CI workflow to their current majors, matching the Prefect reference template. The setup-bonsai v2 bump brings the package injection fallback the workflow-image render step needs.
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
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.
This brings the CI workflow in line with the current
bonsai-rx/prefectreference template, bumping all GitHub Actions and thebonsai-rxcomposites to their current majors:checkout@v7,setup-dotnet@v5,upload-artifact@v7,download-artifact@v8,upload-pages-artifact@v5,deploy-pages@v5,configure-build@v2, andsetup-bonsai@v2. It clears the node20 deprecation warning and moves the workflow off the outdated majors it was generated from.A key change is
setup-bonsai@v2, which adds the package injection fallback from bonsai-rx/setup-bonsai#9: the workflow-image render step should now be able to bootstrap example environments that depend on freshly-built, not-yet-published packages instead of failing at the first bootstrap. This should unblock the render step that has been failing on the open co-development PRs.Best tested together with the example updates in bonsai-rx/machinelearning-examples#39, since the render also depends on the examples matching the current package names and operators.