Skip to content

fix(deps): update fullcalendar family to v7 (main) - #8778

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-major-fullcalendar-family
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-major-fullcalendar-family

Conversation

@renovate

@renovate renovate Bot commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@fullcalendar/core (source) 6.1.22 → 7.1.5 age confidence
@fullcalendar/vue3 (source) 6.1.22 → 7.1.5 age confidence

Release Notes

fullcalendar/fullcalendar (@​fullcalendar/core)

v7.1.5

Compare Source

React
  • FIX: <Activity> (React 19.2+, which Next.js uses to keep recent pages alive) (#​8112):
    • A hidden calendar restarted its timers when re-rendered. Once removed, those timers kept running and kept the whole calendar in memory
    • TimeGrid and DayGrid views shown again jumped back to scrollTime or today's row, losing the user's scroll position
  • FIX: A function event source (events: (info) => …) under a suspended <Suspense> boundary warned "Can't perform a React state update on a component that hasn't mounted yet" when its fetch resolved, and left a timer running (#​8092)
  • FIX: Strict Mode, in development: the now indicator and today's highlight stopped updating after Strict Mode's simulated remount
Event Rendering
  • FIX: DayGrid with dayMaxEvents or dayMaxEventRows:
    • Events hidden behind "+N more" in the last week could hang invisibly past the bottom of the grid, so the month scrolled into empty space (#​7581)
    • When true, a day could hide an event behind "+N more" even when the event and the link both fit, such as showing "+2 more" alone where the first event had room
    • When true, an event that didn't fit at first could only come back cut into pieces around other events, or not at all with eventSlicing: false. It can now come back whole, so some days show events they used to hide. Rarely, a day shows a later event where it used to show part of an earlier one
Headers and Titles
  • FIX: DayGrid (month, multi-month): day headers that name only the weekday gave dayHeaderContent and the other day header hooks a January 1970 date at midnight UTC, which read as the day before west of UTC. date is now a day in view, at midnight in the calendar's time zone. Code that read it in UTC (such as getUTCDay()) should use dow instead (#​7468, #​5854)
  • FIX: TimeGrid: slot headers in the time axis were only as tall as their labels, so a background, border or hover style from slotHeaderClass covered just the top of the slot
  • FIX: List view: listDayFormat: false and listDayAltFormat: false rendered their day headings in the default format instead of turning them off
  • FEATURE: view.titleParts: the title's Intl range parts (type, value, and source of startRange, endRange or shared), so a custom toolbar can style parts of the title, such as a lighter year, in every locale and for ranges. Typed as DateTimeRangeFormatPartWithWeek
  • FEATURE: slotHeaderContent and the other slot header hooks get textParts and the weekdayText, dayNumberText and monthText getters that day cells have (empty strings in the time grid's axis). dayHeaderContent and listDayHeaderContent get monthText too
  • TimeGrid: slot headers between labels have data-time too, like the labeled ones
Event Settings
  • FIX: Dragging an event previewed it differently from how it's handled once dropped:
    • To another resource: its source's constraint, overlap and allow were ignored, so it could be dropped where they forbid, and the preview lost its source's colors and classes
    • An all-day event into TimeGrid's timed area: the preview lost its source's colors and classes
    • Back into the calendar it came from: its source's settings, such as allow, were ignored until dropped
    • In from outside with a resourceId, in views without resources: it didn't take its resource's colors and classes until dropped
  • FIX: Views without resources, such as timeGridWeek with resources loaded: an event added with calendar.addEvent() and no event source didn't get its resource's eventColor, eventClass or other event settings
Resource Views
  • FIX: event.getResources() returned null for each resource that doesn't exist or hasn't been fetched yet. It now leaves them out (#​7300)
  • FIX: Resource Timeline: a resourceColumnsWidth other than a number, px or %, such as '9.5rem', threw an error, so the view didn't render. It now warns and uses the default, 30%. A resource column's width in another unit warns too, and the column still grows to fill the space
  • FIX: Resource Timeline with virtualization: scrolling to a resource added with calendar.addResource(resource, true) could stop a few rows short of it. A regression in v7.1.4
  • FIX: resource.toPlainObject() left out the resource's eventColor
Accessibility
  • FIX: Prev, next, today and custom toolbar buttons had aria-pressed="false", so screen readers announced them as toggle buttons. Only view buttons have it now (#​8042)
  • FIX: A view button alone in its toolbar group had role="tab" with no tablist around it. It's now a toggle button with aria-pressed, like grouped view buttons
Misc
  • FIX: Skeleton CSS: some structural rules, including the z-index ones that set the stacking order, weren't !important, so without cascade layers an app's CSS could override them (though not in a Tailwind app). All are now, so the stacking order is the same in every setup, and a z-* class on an element from a hook, such as tableHeaderClass, has no effect
  • FIX: An event at a wall-clock time skipped by a daylight-saving change (given without an offset) resolves to the time after the change, but startStr/endStr named the skipped time, an hour before start/end. Fed back into addEvent, the string moved the event
  • FIX: TypeScript: calendar.off() required a handler, though calling it without one removes all of that name's handlers added with calendar.on()
  • INTERNAL: every calendar option has a description and a link to its docs page in the source code, for AI agents and other tools that read it
  • INTERNAL: a new, faster test suite on Vitest, replacing Karma

v7.1.4

Compare Source

  • FIX: Resource Timeline with virtualization:
    • Stacked events overflowed onto the rows below when some of the row's events were scrolled out of view. Row heights now fit the events on screen, changing during horizontal scrolling (#​8127)
    • Scrollbar jumped back after fast vertical scrolling and lagged behind the pointer during a drag (#​8135)
    • Possible repeated rerendering when the widest slot label fell out of view
  • FIX: TimeGrid's aria-colcount was one too low, leaving out the time-axis column (#​8124), thx @​ac1982

v7.1.3

Compare Source

Bugfixes
  • FIX: Unable to drag events in DayGrid views when using React 18 Strict Mode (#​8119)
  • FIX: event.setProp('resourceEditable', ...) was ignored with a warning (#​5166)
  • FIX: React "Maximum update depth exceeded" when validRange, visibleRange or hiddenDays is given as a new-but-equal value each render and datesSet sets state (#​7069)
  • FIX: When slotMaxTime is beyond 24h, the now-indicator disappears after midnight in Timeline views, and its arrow disappears in TimeGrid views (#​6394)
  • FIX: eventDrop reports oldResource/newResource when an event that isn't resource-editable is dragged over another resource, even though its resource doesn't change (#​4943)
Locales
  • FEATURE: Tajik locale, available as tg (#​8066)
  • FEATURE: Belarusian locale, available as be (#​7839)
  • FIX: Bulgarian accessibility hints for navigation, more-links, and closing popovers (#​7494)
  • FIX: German and Austrian German list-view hint read "Terminübersichtesansicht" (#​7788)
  • FIX: Czech today button said "now" instead of "today" (#​7674)
  • FIX: Korean navigation, year, list-view, and more-link translations (#​8037)
  • FIX: Farsi empty-calendar and more-link text, year navigation, and accessibility hints (#​8033, #​7546)
  • FIX: Norwegian Nynorsk empty-calendar text and accessibility hints (#​8083, #​6050)

v7.1.2

Compare Source

Accessibility Fixes
  • FIX: Events in DayGrid cells, TimeGrid columns, Timeline lanes and +more popovers are enclosed in a list (role="list", each event in a role="listitem" wrapper), so screen readers can step through them one at a time instead of reading a day or lane as one block
  • FIX: List view, events with a url lost their link semantics, because the listitem role was on the event itself. Events are now wrapped in list items (#​7567)
  • FIX: Day headers (without navLinks), TimeGrid's week-number header and "Timed" row header were read as empty and flagged by axe, because their text was only an aria-label. The text is now visually-hidden content (#​7566, #​6641)
  • FIX: DayGrid day cells' aria-label was ignored or read as blank. The full date is now visually-hidden content, only in cells showing a day number (otherwise the column header already reads the date) (#​7566, #​6637, #​6641, #​7502)
  • FIX: Column-header nav links were labeled "Go to …", which was repeated as the column name for every cell. They're now labeled with just the date (navLinkHint is still used for other nav links)
  • FIX: JAWS switched to forms mode when Tab landed on an event, so the arrow keys did nothing. DayGrid, TimeGrid, MultiMonth and Resource Timeline are now a table (cells role="cell") rather than a grid. Resource Timeline with nested resources or row groups remains a treegrid (#​6641)
  • FIX: Screen readers announced empty "group"s within day cells. Empty wrappers are now role="presentation", and background events, non-business hours and selection highlights are aria-hidden
  • FIX: Resource TimeGrid/DayGrid with filterResourcesWithEvents and datesAboveResources, the blank resource header was an empty columnheader, flagged by axe. It's now an empty cell
  • FIX: Hidden elements used for measurement (+more link, Resource Timeline expander and column divider) use visibility: hidden instead of inert, so none can be focused or read by screen readers

v7.1.1

Compare Source

  • FEATURE: @fullcalendar/mui supports MUI v9 (in addition to v7). MUI skipped v8
  • FEATURE: Resource views, render hooks receive info.resource, the resource of the column/lane being rendered into (#​4926)
    • Event hooks: eventContent, eventClass, eventDidMount, etc, including the *EventTimeClass/*EventTitleClass variants and backgroundEvent* hooks. An event with multiple resources renders once per resource, each with its own info.resource. A dragged event's mirror receives the resource it's being dragged over
    • +more link hooks: moreLinkContent, moreLinkClass, moreLinkDidMount, etc
    • +more popover hooks: the popover's events, as well as dayHeader* and dayCell* hooks where info.inPopover
    • Not populated in non-resource views. Compare info.resource.id, not the object itself, which is not guaranteed to be the same reference across columns
    • New EventTextInfo type, for the arg of *EventTimeClass/*EventTitleClass hooks, which now also receive timeText
  • FIX: Resource TimeGrid/DayGrid, preserve dates with no resources when filterResourcesWithEvents is enabled (#​8099)
    • With datesAboveResources, such a date renders a single non-interactive column with no resource. Day cell/lane hooks for it receive no info.resource, so guard for it:
      dayLaneClass: (info) => info.resource ? `lane-${info.resource.id}` : ''
  • FIX: React 19, "Received an empty string for a boolean attribute inert" warning with dayMaxEvents/eventMaxStack. The offscreen +more link used for measurement also wasn't made inert, so it could receive keyboard focus (#​8114)
  • FIX: Resource TimeGrid/DayGrid, spanning header cells sometimes misaligned with body columns by 1px
  • FIX: Resource Timeline view, with virtualization, leading header cells and slots missing when the timeline is wide enough to not need horizontal scrolling (#​8093)
  • FIX: Resource Timeline view, with virtualization, rows blank until scrolled after removing and re-adding resources within batchRendering, such as for a filter
  • FIX: Resource Timeline view, with virtualization, first resource row hidden or clipped under the header after removing and re-adding resources, such as for a filter, while scrolled at or near the top
  • FIX: Timeline views, printing a timeline that's wide enough to not need horizontal scrolling clips the leading slots, as if scrolled to scrollTime

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! 🎉

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 renovate Bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Aug 25, 2026
@renovate renovate Bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Aug 25, 2026
@renovate

renovate Bot commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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.22
npm error Found: @fullcalendar/core@7.1.5
npm error node_modules/@fullcalendar/core
npm error   @fullcalendar/core@"7.1.5" from the root project
npm error   @fullcalendar/core@"7.1.5" from @fullcalendar/vue3@7.1.5
npm error   node_modules/@fullcalendar/vue3
npm error     @fullcalendar/vue3@"7.1.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @fullcalendar/core@"~6.1.22" from @fullcalendar/daygrid@6.1.22
npm error node_modules/@fullcalendar/daygrid
npm error   @fullcalendar/daygrid@"6.1.22" from the root project
npm error   @fullcalendar/daygrid@"~6.1.22" from @fullcalendar/multimonth@6.1.22
npm error   node_modules/@fullcalendar/multimonth
npm error     @fullcalendar/multimonth@"6.1.22" from the root project
npm error   1 more (@fullcalendar/timegrid)
npm error
npm error Conflicting peer dependency: @fullcalendar/core@6.1.22
npm error node_modules/@fullcalendar/core
npm error   peer @fullcalendar/core@"~6.1.22" from @fullcalendar/daygrid@6.1.22
npm error   node_modules/@fullcalendar/daygrid
npm error     @fullcalendar/daygrid@"6.1.22" from the root project
npm error     @fullcalendar/daygrid@"~6.1.22" from @fullcalendar/multimonth@6.1.22
npm error     node_modules/@fullcalendar/multimonth
npm error       @fullcalendar/multimonth@"6.1.22" 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-11-15T14_23_50_970Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-15T14_23_50_970Z-debug-0.log

@codecov

codecov Bot commented Aug 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 5 times, most recently from e519114 to d04caad Compare September 2, 2026 00:15
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 7 times, most recently from 99a7284 to 704cd42 Compare September 9, 2026 13:30
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch from 704cd42 to aa8a9a5 Compare September 10, 2026 19:12
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch from aa8a9a5 to 3251113 Compare September 15, 2026 10:31
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch from 3251113 to 1f1f49c Compare September 24, 2026 09:55
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 2 times, most recently from c195512 to 5ccd6f2 Compare October 5, 2026 13:04
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 3 times, most recently from 523e24b to d7f7170 Compare October 13, 2026 00:23
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 2 times, most recently from f685930 to 16f4dda Compare October 16, 2026 04:22
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 4 times, most recently from 054d36e to f11b077 Compare October 26, 2026 20:06
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 5 times, most recently from 988bc64 to 93891c9 Compare November 6, 2026 00:28
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch 2 times, most recently from f2e6928 to 821b565 Compare November 13, 2026 02:08
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/main-major-fullcalendar-family branch from 821b565 to ef404f0 Compare November 15, 2026 14:23

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants