Repository navigation
Deprecate the notify-flux action - #38
Merged
Merged
Conversation
Flux polls for OCI deployment bundles, so nothing needs to poke a Receiver. The action now warns when it runs and goes in the next major release.
lewisjared
force-pushed
the
chore/remove-notify-flux
branch
from
September 16, 2026 13:36
0e0ae2d to
db053bc
Compare
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.
Deprecates the
notify-fluxaction instead of removing it, so this can ship in a minor release. The action still works, but it now emits a workflow warning telling the caller to drop the step. Its README and the top-level README say it is deprecated and goes in the next major release.Every service now deploys from an OCI bundle that Flux finds by polling, and climate-resource/infrastructure#705 removes the last Receiver. No workflow in the organisation still uses the action.