Bump prometheus-operator jsonnet pin in CMO alongside merge#148
Open
machine424 wants to merge 2 commits into
Open
Bump prometheus-operator jsonnet pin in CMO alongside merge#148machine424 wants to merge 2 commits into
machine424 wants to merge 2 commits into
Conversation
Alongside the prometheus-operator merge job, derive the release branch from the upstream tag and update the jsonnet pin in CMO's jsonnetfile.json (scoped to only the prometheus-operator dependency). Skips if already on the latest release branch to avoid overlapping with the general jsonnet deps update workflow. Also exposes upstream-release as an output of merge-flow.yaml.
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.
Alongside the prometheus-operator merge job, derive the release
branch from the upstream tag and update the jsonnet pin in CMO's
jsonnetfile.json (scoped to only the prometheus-operator dependency).
Skips if already on the latest release branch to avoid overlapping
with the general jsonnet deps update workflow.
Also exposes upstream-release as an output of merge-flow.yaml.