chore(deps): bump fullcalendar from 3.10.5 to 6.1.21

[dependabot]

Bumps fullcalendar from 3.10.5 to 6.1.21.

Release notes

Sourced from fullcalendar's releases.

v6.1.21

• feature: Angular 22 support (#8074)

v6.1.20

• feature: Angular 21 support (#8015)

📢 FYI, read an update about v7 »

v6.1.19

• feature: Angular 20 support (#7946)
• feature: setting to control how nowIndicator displays in all-day slots (#6175) (nowIndicatorSnap; use false to ensure time-granularity always)
• fix: allow business hours that START past midnight (#7934)

v6.1.18

• fix: Optimize custom content-injection rerendering performance (#3003, #7650) (Especially important for event rerendering with eventContent)

v6.1.17

• fix: recurring event start/end time not updated when timezone changed (#5273)
• fix: nowIndicator not updated when timezone changed (#5753)
• fix: nowIndicator lags after returning to suspended tab (#7806)
• fix: "today" date does not update after current time crosses midnight (#3783)
• fix: day header 1 day behind with Luxon & timezone with midnight DST (#7633)
• fix: in timeline, incorrect navLink for granularities other than day/week (#4931)
• fix: validRange in multiMonth view does not render all the days (#7287)
• angular: Accept TempateRef for resourceAreaColumns.cellContent (#7894), thx @​gongAll

v6.1.16

Angular

• Angular 19 support (#7824)

v6.1.15

General

• fix: dragScroll does not work on multiMonth view (#7324)
• fix: clicking on nowIndicator line ignores the event behind (#6801)
• fix: dates not selectable in Shadow DOM since v6.1.12 (#7685)

React

• fix: adaptive print version shows events with custom eventContent with zero height (#7419)

v6.1.14

React

• React 19 support

Angular

... (truncated)

Changelog

Sourced from fullcalendar's changelog.

v7.0.2

• 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

• 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

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)

v7.0.0-rc.3

• FIX: In React, event flicker after event drag-n-drop
• FIX: In React/Preact, expose the CalendarRef type
• FIX: In TimeGrid view, when snapDuration smaller than slotDuration, incorrect date-selection coordinates
• FIX: With custom slotHeaderFormats, navLinks sometimes disabled (#8064)
• FIX: For Shadcn/MUI toolbars, or users of CalendarController, button hints wrong for certain locales
• FEATURE: Warn on unknown options
• FEATURE: Warn on invalid class-name inputs
• BREAKING: Renamed a few things for consistency. Apologies. Please update any forked themes.
  • Renamed info-prop .multiMonthColumnCount to .multiMonthColumns

... (truncated)

Commits

• See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
fullcalendar	[>= 5.a, < 6]

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)

[DeepDiver1975]

Holding: CI is failing (not a rebase conflict). Failing check(s): JS Unit / Javascript Unit. First failure: JS Unit / Javascript Unit. A rebase won't fix this — needs a human/upstream fix.

[DeepDiver1975]

Holding: CI is failing (not a rebase conflict) — root-cause refinement, supersedes my earlier comment on this PR (which only named the failing check). Run 30222363164 is past log retention (HTTP 410), so this was re-derived structurally from gulpfile.js plus npm registry metadata.

FullCalendar 4 removed the jQuery-plugin distribution, and 6.x has no dist/ bundle at all. Registry metadata:

version	type	main	peers
3.10.5	commonjs	dist/fullcalendar.js	jquery: 2 - 3, moment: ^2.20.1
6.1.21	module	./index.cjs	(none)

gulpfile.js bundles FullCalendar by hard-coded dist/ path:

'node_modules/fullcalendar/dist/fullcalendar.js',    // line 63
'node_modules/fullcalendar/dist/locale-all.js',      // line 64
'node_modules/fullcalendar/dist/fullcalendar.css',   // line 73

None of those files exist in 6.1.21, so the vendor bundle is built without FullCalendar and the jQuery plugin entry point ($.fullCalendar) is simply absent — which is what takes out JS Unit / Javascript Unit.

This is a real source migration to the @fullcalendar/* ESM packages (and away from the jQuery plugin and moment), not something a rebase or a lockfile refresh can fix.