Pin Flux version for CI to v0.48.0#130
Merged
mplegendre merged 1 commit intollnl:develfrom Feb 6, 2026
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
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.
The CI testing container for Flux was specifying the image tag
noble, which is the most recent version using Ubuntu noble (24.04). That tag was recently updated with a new development version of Flux which changes something such that it no longer accepts the broker.toml config file we use, causing the cluster to fail to start.This fixes the problem by pinning Flux to the current most recent release, v0.48.0. This restores the Flux CI to functionality.