chore(deps): pin dependencies

[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

Package	Type	Update	Change
@playwright/browser-chromium (source)	devDependencies	pin	^1.61.1 → 1.61.1
@playwright/test (source)	devDependencies	pin	^1.61.1 → 1.61.1
@testing-library/dom	devDependencies	pin	^10.4.1 → 10.4.1
@testing-library/jest-dom	devDependencies	pin	^6.9.1 → 6.9.1
@testing-library/react	devDependencies	pin	^16.3.2 → 16.3.2
@testing-library/user-event	devDependencies	pin	^14.6.1 → 14.6.1
@vitest/coverage-v8 (source)	devDependencies	pin	^4.1.10 → 4.1.10
jsdom	devDependencies	pin	^29.1.1 → 29.1.1
msw (source)	devDependencies	pin	^2.15.0 → 2.15.0
vitest (source)	devDependencies	pin	^4.1.10 → 4.1.10

---

Warning

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

⚠️ Renovate's pin functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "before 7am on Monday"
• 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.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[dsimansk]

/ok-to-test

[openshift-ci]

@red-hat-konflux-kflux-prd-rh02[bot]: all tests passed!

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.

[dsimansk]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, 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:

• OWNERS [dsimansk]

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