Skip to content

chore(deps): refresh rpm lockfiles (release-1.20) [SECURITY]#916

Open
red-hat-konflux[bot] wants to merge 1 commit intorelease-1.20from
konflux/mintmaker/release-1.20-release-1.20/lock-file-maintenance-vulnerability
Open

chore(deps): refresh rpm lockfiles (release-1.20) [SECURITY]#916
red-hat-konflux[bot] wants to merge 1 commit intorelease-1.20from
konflux/mintmaker/release-1.20-release-1.20/lock-file-maintenance-vulnerability

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

@red-hat-konflux red-hat-konflux Bot commented May 5, 2026

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

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


Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/release-1.20-release-1.20/lock-file-maintenance-vulnerability branch 8 times, most recently from 2aa56c1 to eb2d560 Compare May 6, 2026 11:21
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/release-1.20-release-1.20/lock-file-maintenance-vulnerability branch from eb2d560 to efe8800 Compare May 6, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants