build(deps): Bump @tanstack/virtual-core from 3.13.6 to 3.13.18 in /frontend

[dependabot]

Bumps @tanstack/virtual-core from 3.13.6 to 3.13.18.

Release notes

Sourced from @​tanstack/virtual-core's releases.

@​tanstack/virtual-core@​3.13.18

Patch Changes

• revert(virtual-core): "notify framework when count changes" 2542c5a (#1112)

@​tanstack/virtual-core@​3.13.17

Patch Changes

• fix(virtual-core): preserve auto alignment for visible items when scrolling (#1110)

@​tanstack/virtual-core@​3.13.16

Patch Changes

• fix(virtual-core): improve scrollToIndex reliability in dynamic mode (#1106)
  • Wait extra frame for ResizeObserver measurements before verifying position
  • Abort pending scroll operations when new scrollToIndex is called

@​tanstack/virtual-core@​3.13.15

Patch Changes

• fix(virtual-core): scroll to last index properly (#1105)

@​tanstack/virtual-core@​3.13.14

Patch Changes

• Fix: Correct lane assignments when lane count changes dynamically (#1095)

  Fixed a critical bug where changing the number of lanes dynamically would cause layout breakage with incorrect lane assignments. When the lane count changed (e.g., from 3 to 2 columns in a responsive masonry layout), some virtual items would retain their old lane numbers, causing out-of-bounds errors and broken layouts.

  Root Cause: After clearing measurements cache on lane change, the virtualizer was incorrectly restoring data from initialMeasurementsCache, which contained stale lane assignments from the previous lane count.

  Fix: Skip initialMeasurementsCache restoration during lane transitions by checking the lanesSettling flag. This ensures all measurements are recalculated with correct lane assignments for the new lane count.

  Before:

  // With lanes = 2
  virtualItems.forEach((item) => {
    columns[item.lane].push(item) // ❌ Error: item.lane could be 3
  })

  After:

  // With lanes = 2
  virtualItems.forEach((item) => {
    columns[item.lane].push(item) // ✅ item.lane is always 0 or 1
  })

... (truncated)

Changelog

Sourced from @​tanstack/virtual-core's changelog.

3.13.18

Patch Changes

• revert(virtual-core): "notify framework when count changes" 2542c5a (#1112)

3.13.17

Patch Changes

• fix(virtual-core): preserve auto alignment for visible items when scrolling (#1110)

3.13.16

Patch Changes

• fix(virtual-core): improve scrollToIndex reliability in dynamic mode (#1106)
  • Wait extra frame for ResizeObserver measurements before verifying position
  • Abort pending scroll operations when new scrollToIndex is called

3.13.15

Patch Changes

• fix(virtual-core): scroll to last index properly (#1105)

3.13.14

Patch Changes

• Fix: Correct lane assignments when lane count changes dynamically (#1095)

  Fixed a critical bug where changing the number of lanes dynamically would cause layout breakage with incorrect lane assignments. When the lane count changed (e.g., from 3 to 2 columns in a responsive masonry layout), some virtual items would retain their old lane numbers, causing out-of-bounds errors and broken layouts.

  Root Cause: After clearing measurements cache on lane change, the virtualizer was incorrectly restoring data from initialMeasurementsCache, which contained stale lane assignments from the previous lane count.

  Fix: Skip initialMeasurementsCache restoration during lane transitions by checking the lanesSettling flag. This ensures all measurements are recalculated with correct lane assignments for the new lane count.

  Before:

  // With lanes = 2
  virtualItems.forEach((item) => {
    columns[item.lane].push(item) // ❌ Error: item.lane could be 3
  })

  After:

... (truncated)

Commits

• 5d6acc9 ci: Version Packages (#1113)
• 9067574 revert(virtual-core): "notify framework when count changes" (#1112)
• c48b2ac ci: Version Packages (#1111)
• 21d9a46 fix(virtual-core): preserve auto alignment for visible items when scrolling (...
• 7fd2654 ci: Version Packages (#1107)
• db6df21 fix(virtual-core): improve scrollToIndex reliability in dynamic mode
• 0bcf14d ci: Version Packages (#1102)
• 5a273bf fix(virtual-core): scroll to last index properly (#1105)
• a1d0043 ci: Version Packages (#1101)
• 6d9274c fix(virtual-core): correct lane assignments when lane count changes dynamical...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​tanstack/virtual-core since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[roborev-ci]

roborev: Combined Review (b9f233b)

Verdict: No Medium, High, or Critical issues found; this dependency bump looks clean.

All four reviews reported no issues in the diff (@tanstack/virtual-core 3.13.6 → 3.13.18 with corresponding frontend/package-lock.json updates).

---

Synthesized from 4 reviews (agents: codex, gemini | types: default, security)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.