chore(deps): lock file maintenance

[red-hat-konflux]

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/New_York)

• 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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e143cac6-09fc-40e3-bc0a-5b39e010ee35

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[amber-review-bot]

Amber review

Status: Complete

View the submitted review.

[amber-review-bot]

Verdict

Low-risk automated lock-file maintenance: pnpm-lock.yaml is the only changed file, with 43 in-place transitive dependency bumps and no package.json edits, so no declared version ranges change. All updates are patch/minor (e.g. jose 6.2.10 -> 6.2.11, postcss 8.5.26 -> 8.5.28, browserslist 4.28.8 -> 4.28.9), and none touch Go, control-plane, pod specs, secrets, or API surfaces.

Review notes

• No production source, manifest, or test code changes; HyperShell backend/control-plane conventions (panic, error wrapping, SecurityContext, reconcile pattern, secrets handling) are not exercised by this diff.
• The one larger jump is confbox 0.2.4 -> 0.3.1 (minor, transitive via pkg-types); no direct consumer changes and it stays within resolved ranges.
• Security-relevant bump jose 6.2.10 -> 6.2.11 is a patch and generally desirable to take.
• Recommend CI (pnpm ... check, frontend build/tests) is green before merge, as is standard for lock refreshes.

Cross-PR coordination

No material cross-PR coordination issue requires maintainer action.

Previous concerns

No prior Amber findings exist for this pull request in the review history, so there is nothing to re-verify.

Findings Summary (ordered by severity, highest first):

None.

Convention Checklist:

Convention	Result
Dependency updates confined to lock file (no range changes)	Pass
Conventional commit message	Pass