Skip to content

NO-ISSUE: Lock file maintenance - #707

Open
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/lock-file-maintenance
Open

NO-ISSUE: Lock file maintenance#707
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/lock-file-maintenance

Conversation

@red-hat-konflux-kflux-prd-rh02

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Between 12:00 AM and 04:59 AM (* 0-4 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@osac-ci-bot osac-ci-bot changed the title Lock file maintenance NO-ISSUE: Lock file maintenance Sep 2, 2026
@openshift-ci

openshift-ci Bot commented Sep 2, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux-kflux-prd-rh02[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:

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

@openshift-ci-robot

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh02[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

[!WARNING]
Some dependencies could not be looked up. Check the warning logs for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
  • Between 12:00 AM and 04:59 AM (* 0-4 * * *)
  • Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

E2E on lgtm

Label lgtm applied — starting expensive e2e (PR run replay).

  • Started: 0/3
  • Already active/green (skipped rerun): 3

@osac-ci-bot
osac-ci-bot added this pull request to the merge queue Sep 2, 2026
@omer-vishlitzky
omer-vishlitzky removed this pull request from the merge queue due to a manual request Sep 2, 2026
@omer-vishlitzky

Copy link
Copy Markdown
Contributor

/hold

ajamias pushed a commit to ajamias/osac that referenced this pull request Sep 3, 2026
## Summary
- Always report cheap CI names on every PR/`merge_group` (skip on steps)
so they can be required without hanging the merge queue. Same pattern as
generated-code (PR osac-project#699).
- Rename colliding `Run Tests` jobs to `Run unit tests (osac-operator)`
and `Run unit tests (bare-metal-fulfillment-operator)`.
- Triggered by [osac-project#707](osac-project#707):
`ansible-lint` went red on a lock bump and was not a merge gate.

Enforce the new names via
[osac-project/github-config#205](osac-project/github-config#205)
(`repo_osac.required_status_checks`). Do not edit the live
`ci-status-checks` ruleset in this repo; tofu apply overwrites it.

## Test plan
- [ ] This PR: named checks report (green no-op or real run). No extra
image builds on unrelated paths.
- [ ] After github-config#205 applies: a docs-only / unrelated-component
PR still merges (names report, work skipped).
- [ ] An `osac-aap` change still has to pass `ansible-lint` before
merge.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary

- **CI:** Updated workflows to run on pull requests and `merge_group`
events. Moved path filtering into jobs so required checks remain visible
in the merge queue. Pinned GitHub Actions and disabled persisted
checkout credentials.
- **Tests:** Added conditional execution for Ansible, image, Helm,
Darwin, fulfillment-service, dependency-review, and generated-code
checks. Filter failures now fail the relevant check. Renamed colliding
`Run Tests` checks.
- **Deployment:** Prevented image and manifest publishing during
`merge_group` events.
- **Documentation:** Updated the documented required generated-code
checks.
- **API surface, controllers, database, and auth:** No changes.
- **Backward compatibility:** No runtime behavior changes. CI trigger,
required status-check, and merge queue behavior changes. After merge,
update `ci-status-checks` with the requested contexts and retain
`strict_required_status_checks_policy: false`.

## Risk classification

**risk:show** — The changes affect CI workflow triggers, required status
checks, merge queue behavior, action pinning, and image publishing
conditions. They do not modify application runtime code, APIs, data,
authentication, or production deployment logic.

This is not **risk:ship** because CI configuration changes can affect
merge eligibility and artifact publication. It does not qualify as
**risk:ask** because the workflows include explicit filtering, failure
handling, conditional execution, and merge-queue safeguards.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Min Zhang <minzhang@redhat.com>
@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/main/lock-file-maintenance branch from 1700bdd to 9f265dd Compare September 3, 2026 08:08
@openshift-ci openshift-ci Bot removed the lgtm label Sep 3, 2026
@openshift-ci

openshift-ci Bot commented Sep 3, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot changed the title NO-ISSUE: Lock file maintenance Lock file maintenance Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Removed ok-to-test label due to new commits. An org member must re-approve with /ok-to-test.

@osac-ci-bot osac-ci-bot changed the title Lock file maintenance NO-ISSUE: Lock file maintenance Sep 3, 2026
@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/main/lock-file-maintenance branch from 9f265dd to 03a5ca5 Compare September 4, 2026 08:09
@openshift-ci openshift-ci Bot removed the lgtm label Sep 4, 2026
@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot changed the title NO-ISSUE: Lock file maintenance Lock file maintenance Sep 4, 2026
@openshift-ci

openshift-ci Bot commented Sep 4, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

Removed ok-to-test label due to new commits. An org member must re-approve with /ok-to-test.

Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/main/lock-file-maintenance branch from 03a5ca5 to bd637db Compare September 5, 2026 08:09
@openshift-ci openshift-ci Bot removed the lgtm label Sep 5, 2026
@openshift-ci

openshift-ci Bot commented Sep 5, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown

E2E on lgtm

Label lgtm applied — starting expensive e2e (PR run replay).

  • Started: 0/3
  • Already active/green (skipped rerun): 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants