fix(deps): update fullcalendar family to v7 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@fullcalendar/core (source)	6.1.21 → 7.1.0
@fullcalendar/vue3 (source)	6.1.21 → 7.1.0

---

Release Notes

fullcalendar/fullcalendar (@​fullcalendar/core)

v7.1.0

Compare Source

Event Rendering

• PERF: DayGrid with large number of events, when dayMaxEvents:true (limited by natural row height), only a necessary subset of events will be DOM-inserted, not all
  • BREAKING: As a result, a subset of events will be run through event render hooks like eventContent
• DayGrid event slicing
  • FEATURE: Better event packing, including smarter positioning decisions for fewer slices
  • FEATURE: Related slices have more similar y-coordinates
  • FIX: Events unnecessarily going to +more link when higher-level slot would accommodate
• TimeGrid event positioning
  • FIX: Events with custom ordering and eventOrderStrict:true can overlap with slotEventOverlap: false (#​7914)
  • FIX: Overlapping events can have tiny width when event content not visible (#​7879)
• FIX: In Timeline and TimeGrid, when custom eventOrder, DOM order respects start-time first, then eventOrder. Better for a11y and tabbing through events sequentially
• FIX: React StrictMode: DayGrid events permanently invisible (#​8088)

Resource Views

• FIX: Timeline view, smoother virtualized fast scrolling, especially with trackpad and especially while scrolling up with irregular height resource rows
• FIX: Timeline view, account for DST in timeslots (#​7620)
• FIX: Resource TimeGrid/DayGrid, filterResourcesWithEvents should exclude columns (#​6149)

Print Rendering

• FEATURE: Print renders business-hours for print-previews that enable it
• FIX: Better page-wrapping of tall DayGrid rows with many events
• FIX: Better page-wrapping of tall Resource-Timeline rows with many events
• FIX: Events are not visible when we print using window.print() (#​8097)

Misc

• PERF: General improvements with option-changes. Users of @fullcalendar/preact must upgrade their preact peer dependency to >=10.29.8
• FIX: Screen-reader improvement for Resource-Timeline timeline header text

v7.0.2

Compare Source

• FEATURE: Restored Bootstrap 5 support (originally omitted from v7) (#​8040)
• FIX: Vue 3 types for template ref for getApi (#​8086)
• FIX: Angular DOM-insertion JS error with #eventContent (#​8085)

v7.0.1

Compare Source

• Better screen reader experience for users of Resource Timeline view
• printMaxRows setting to control print-rendering cutoff for Resource Timeline view
• Salesforce LWC component (beta), zip files on each release (#​6196)

v7.0.0

Compare Source

Changes since v6

Lots! 🎉

• 📋 Full Changelog
• 📚 V7 Docs
• 🎨 Theme system justification
• 🛝 Theme playground

Changes since v7 pre-releases

• FEATURE: Angular 22 support (#​8074)
• FIX: Resource timeline rows keep a stale height after their events are removed (#​8078)
• FIX: With showNonCurrentDates, events on first or last week of month disappear upon navigation (#​8077)
• FIX: With virtualization, resource invisible after adding resource manually (#​8072)
• BREAKING: Need temporal-polyfill@^1.0.1 as peerDependency
• BREAKING: Some CDN URLs changed:
  • /all.global.js -> /all/global.js
  • /locales-all.global.js -> /locales-all/global.js
  • /locales/es.global.js -> /locales/es/global.js (and other locales)

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • "before 5am on wednesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @fullcalendar/daygrid@6.1.21
npm error Found: @fullcalendar/core@7.1.0
npm error node_modules/@fullcalendar/core
npm error   @fullcalendar/core@"7.1.0" from the root project
npm error   @fullcalendar/core@"7.1.0" from @fullcalendar/vue3@7.1.0
npm error   node_modules/@fullcalendar/vue3
npm error     @fullcalendar/vue3@"7.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @fullcalendar/core@"~6.1.21" from @fullcalendar/daygrid@6.1.21
npm error node_modules/@fullcalendar/daygrid
npm error   @fullcalendar/daygrid@"6.1.21" from the root project
npm error   @fullcalendar/daygrid@"~6.1.21" from @fullcalendar/multimonth@6.1.21
npm error   node_modules/@fullcalendar/multimonth
npm error     @fullcalendar/multimonth@"6.1.21" from the root project
npm error   1 more (@fullcalendar/timegrid)
npm error
npm error Conflicting peer dependency: @fullcalendar/core@6.1.21
npm error node_modules/@fullcalendar/core
npm error   peer @fullcalendar/core@"~6.1.21" from @fullcalendar/daygrid@6.1.21
npm error   node_modules/@fullcalendar/daygrid
npm error     @fullcalendar/daygrid@"6.1.21" from the root project
npm error     @fullcalendar/daygrid@"~6.1.21" from @fullcalendar/multimonth@6.1.21
npm error     node_modules/@fullcalendar/multimonth
npm error       @fullcalendar/multimonth@"6.1.21" from the root project
npm error     1 more (@fullcalendar/timegrid)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-05T04_22_37_278Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-05T04_22_37_278Z-debug-0.log

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!