chore: update pnpm 10.33.2 -> 10.34.6 to fix CVE-2026-101043

[dkarpele]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5dab4e83-1cf0-422c-8871-4bb73b3ecc1d

📥 Commits

Reviewing files that changed from the base of the PR and between f57d6ff and 28bc23b.

📒 Files selected for processing: 3

• .konflux/Containerfile.plugin
• Dockerfile
• package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the package manager used by project configuration and build environments from pnpm 10.33.2 to 10.34.6. This update applies consistently across the project’s build setup. No end-user-facing feature or behavior changes are included in this release.

The project package manager declaration and both build environments now use pnpm 10.34.6 instead of 10.33.2.

Changes: pnpm Version Update

Layer / File(s)	Summary
pnpm version alignment package.json, Dockerfile, .konflux/Containerfile.plugin	The package manager declaration and both build configurations now use pnpm 10.34.6.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 28bc2

The package manager version is consistent across the manifest, build images, and CI, so this change presents no material merge risk.

Pre-merge checks: 4 · 1

Failed checks: 1 inconclusive

Check name	Status	Explanation	Resolution
Description check		No pull request description was provided, so the change context cannot be assessed from the description.	Add a brief description that explains the pnpm version update and its purpose, including the CVE reference.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly identifies the pnpm upgrade from 10.33.2 to 10.34.6 and states its security purpose.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 12.75%. Comparing base (3bd1dab) to head (28bc23b).
⚠️ Report is 59 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #308      +/-   ##
==========================================
+ Coverage   11.30%   12.75%   +1.45%     
==========================================
  Files         169      173       +4     
  Lines        6679     6858     +179     
  Branches     2235     2322      +87     
==========================================
+ Hits          755      875     +120     
+ Misses       5923     5742     -181     
- Partials        1      241     +240     

Flag	Coverage Δ
unit-tests	12.75% <ø> (+1.45%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.