Skip to content

chore: weekly dependency updates#1400

Open
github-actions[bot] wants to merge 4 commits into
masterfrom
chore/weekly-deps-update
Open

chore: weekly dependency updates#1400
github-actions[bot] wants to merge 4 commits into
masterfrom
chore/weekly-deps-update

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated weekly dependency updates generated by GitHub Actions.

This workflow updates dependencies across the workspace and refreshes the lockfile.

@changeset-bot

changeset-bot Bot commented Jun 14, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: fadeb9d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@itwin/presentation-hierarchies-react Patch
@itwin/unified-selection Patch
@itwin/presentation-hierarchies Patch
@itwin/presentation-shared Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@grigasp grigasp marked this pull request as ready for review June 15, 2026 06:56
@grigasp grigasp requested a review from a team as a code owner June 15, 2026 06:56
Copilot AI review requested due to automatic review settings June 15, 2026 06:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Automated weekly dependency refresh across the workspace, updating catalog-pinned versions and a few app/tooling dependencies, plus adding a changeset to publish patch releases for affected packages.

Changes:

  • Bumped catalog versions for iTwin.js core/dev packages, build tools, Node types, and test tooling (e.g., happy-dom).
  • Updated a few workspace package dependencies (e.g., lage, sass, vite-plugin-static-copy, OpenTelemetry deps).
  • Added a changeset to publish patch bumps for impacted published packages.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
pnpm-workspace.yaml Updates shared dependency catalog versions (notably iTwin.js core/dev and test/build tooling).
package.json Bumps lage patch version.
apps/test-app/frontend/package.json Bumps sass and vite-plugin-static-copy.
apps/test-app/backend/package.json Bumps OpenTelemetry resource/trace-base versions.
apps/full-stack-tests/package.json Bumps sass version used in full-stack tests.
.changeset/every-games-run.md Adds a changeset for patch releases of affected packages.

Comment thread .changeset/every-games-run.md

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unified selection benchmark

Benchmark suite Current: fadeb9d Previous: 758a1cc Deviation Status
compute selection for 50k elements 314 ms 391 ms -19.69%
compute selection for 50k elements (P95 of main thread blocks) 34 ms 31 ms 9.68% 〰️
compute parent selection for 50k elements 286 ms 355 ms -19.44%
compute parent selection for 50k elements (P95 of main thread blocks) 34 ms 31 ms 9.68% 〰️
compute top ancestor selection for 50k elements 458 ms 551 ms -16.88%
compute top ancestor selection for 50k elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute category selection for 50k elements 79 ms 103 ms -23.30% 〰️
compute category selection for 50k elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute model selection for 50k elements 61 ms 84 ms -27.38% 〰️
compute model selection for 50k elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute functional selection for 50k 3D elements 348 ms 437 ms -20.37%
compute functional selection for 50k 3D elements (P95 of main thread blocks) 31 ms 35 ms -11.43% 〰️
compute parent functional selection for 50k 3D elements 374 ms 464 ms -19.40%
compute parent functional selection for 50k 3D elements (P95 of main thread blocks) 35 ms 34 ms 2.94% 〰️
compute top ancestor functional selection for 50k 3D elements 1033 ms 1212 ms -14.77%
compute top ancestor functional selection for 50k 3D elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute functional selection for 50k 2D elements 2478 ms 3210 ms -22.80%
compute functional selection for 50k 2D elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute parent functional selection for 50k 2D elements 2496 ms 3182 ms -21.56%
compute parent functional selection for 50k 2D elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
compute top ancestor functional selection for 50k 2D elements 2632 ms 3114 ms -15.48%
compute top ancestor functional selection for 50k 2D elements (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
hilite 50k elements 1009 ms 1277 ms -20.99%
hilite 50k elements (P95 of main thread blocks) 40 ms 54 ms -25.93% 〰️
hilite 50k group elements 185 ms 251 ms -26.29%
hilite 50k group elements (P95 of main thread blocks) 33 ms 31 ms 6.45% 〰️
hilite 1k subjects 37013 ms 49152 ms -24.70%
hilite 1k subjects (P95 of main thread blocks) 0 ms 25 ms -100% 〰️
hilite 50k subcategories 245 ms 309 ms -20.71%
hilite 50k subcategories (P95 of main thread blocks) 40 ms 41 ms -2.44% 〰️
hilite 50k functional 3D elements 22781 ms 29420 ms -22.57%
hilite 50k functional 3D elements (P95 of main thread blocks) 41 ms 42 ms -2.38% 〰️
hilite 50k functional 2D elements 5068 ms 6631 ms -23.57%
hilite 50k functional 2D elements (P95 of main thread blocks) 45 ms 44 ms 2.27% 〰️

This comment was automatically generated by workflow using github-action-benchmark.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hierarchies benchmark

Benchmark suite Current: fadeb9d Previous: b45481d Deviation Status
filtering filters with 50000 paths 8621 ms 6632 ms 29.99% 🚨
filtering filters with 50000 paths (P95 of main thread blocks) 245 ms 169 ms 44.97% 🚨
hide if no children required to finalize root, w/o children 40724 ms 28777 ms 41.52% 🚨
hide if no children required to finalize root, w/o children (P95 of main thread blocks) 54 ms 38 ms 42.11% 〰️
hide if no children required to finalize root, w/ children 189 ms 133 ms 42.11% 🚨
hide if no children required to finalize root, w/ children (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
models tree initial (Baytown) 81 ms 65 ms 24.62% 〰️
models tree initial (Baytown) (P95 of main thread blocks) 0 ms 0 ms 0% 🟰
models tree full (Baytown) 7198 ms 5744 ms 25.31% 🚨
models tree full (Baytown) (P95 of main thread blocks) 91 ms 65 ms 40% 〰️
models tree creates initial filtered view for 50k target items 2367 ms 1729 ms 36.90% 🚨
models tree creates initial filtered view for 50k target items (P95 of main thread blocks) 213 ms 42 ms 407.14% 🚨
grouping by label 14904 ms 11605 ms 28.43% 🚨
grouping by label (P95 of main thread blocks) 71 ms 54 ms 31.48% 〰️
grouping by class 14765 ms 11549 ms 27.85% 🚨
grouping by class (P95 of main thread blocks) 43 ms 39 ms 10.26% 〰️
grouping by property 15554 ms 12079 ms 28.77% 🚨
grouping by property (P95 of main thread blocks) 64 ms 49 ms 30.61% 〰️
grouping by base class (10 classes) 13813 ms 10678 ms 29.36% 🚨
grouping by base class (10 classes) (P95 of main thread blocks) 118 ms 98 ms 20.41% 〰️
grouping by multiple attributes 31718 ms 24576 ms 29.06% 🚨
grouping by multiple attributes (P95 of main thread blocks) 54 ms 59 ms -8.47% 〰️
flat 50k elements list 4749 ms 3782 ms 25.57% 🚨
flat 50k elements list (P95 of main thread blocks) 70 ms 52 ms 34.62% 〰️

This comment was automatically generated by workflow using github-action-benchmark.

@grigasp grigasp disabled auto-merge June 15, 2026 07:03
@grigasp

grigasp commented Jun 15, 2026

Copy link
Copy Markdown
Member

Reviewing hierarchies benchmark regressions...

Update: In majority of cases, the baseline was exceptionally fast (better than average). Having said that, the 3 runs we have in this PR are worse than average. Also, the baseline has a few runs worse than average (grouping ones), but the runs in this PR are even worse. Will wait a bit and rerun to see if this is not just some pipelines' slowdown.

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.

3 participants