NO-JIRA: update rh-manifest.txt

[openshift-monitoring-bot]

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.
If you wish to perform this manually, execute the following commands from openshift/prometheus repo:

git fetch https://github.com/prometheus/prometheus --tags
if ! git merge refs/tags/v3.9.1 --no-edit; then
  git checkout --theirs CHANGELOG.md VERSION go.mod go.sum .golangci.yml
  git checkout --ours plugins.yml plugins
  git add CHANGELOG.md VERSION go.mod go.sum .golangci.yml plugins.yml plugins
  git merge --continue
fi
go mod tidy
go mod vendor
# Only compress assets if assets actually changed
# The git diff relies on gits remote naming. The merge-flow checks out
# $downstream as origin at the time of writing this code.
if ! git diff --exit-code origin/main web/ui; then
  make assets-compress
  find web/ui/static -type f -name '*.gz' -exec git add {} \;
  git add web/ui/embed.go
  git diff --cached --exit-code || git commit -s -m "[bot] assets: generate"
fi

if [ -f scripts/rh-manifest.sh ]; then
  bash scripts/rh-manifest.sh
  git add rh-manifest.txt
  git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

[machine424]

/retitle NO-JIRA: update rh-manifest.txt
/retest-required
/lgtm
/verified by existing tests

[openshift-ci-robot]

@machine424: This PR has been marked as verified by existing tests.

Details

In response to this:

/retitle NO-JIRA: update rh-manifest.txt
/retest-required
/lgtm
/verified by existing tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@openshift-monitoring-bot[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.
If you wish to perform this manually, execute the following commands from openshift/prometheus repo:

git fetch https://github.com/prometheus/prometheus --tags
if ! git merge refs/tags/v3.9.1 --no-edit; then
 git checkout --theirs CHANGELOG.md VERSION go.mod go.sum .golangci.yml
 git checkout --ours plugins.yml plugins
 git add CHANGELOG.md VERSION go.mod go.sum .golangci.yml plugins.yml plugins
 git merge --continue
fi
go mod tidy
go mod vendor
# Only compress assets if assets actually changed
# The git diff relies on gits remote naming. The merge-flow checks out
# $downstream as origin at the time of writing this code.
if ! git diff --exit-code origin/main web/ui; then
 make assets-compress
 find web/ui/static -type f -name '*.gz' -exec git add {} \;
 git add web/ui/embed.go
 git diff --cached --exit-code || git commit -s -m "[bot] assets: generate"
fi

if [ -f scripts/rh-manifest.sh ]; then
 bash scripts/rh-manifest.sh
 git add rh-manifest.txt
 git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, openshift-monitoring-bot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [machine424]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@openshift-monitoring-bot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ginkgo-tests-cmo	4c24858	link	false	/test ginkgo-tests-cmo

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.