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

fix(deps): update fullcalendar family to v7 (main)#8778
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.217.0.2 age confidence
@fullcalendar/vue3 (source) 6.1.217.0.2 age confidence

Release Notes

fullcalendar/fullcalendar (@​fullcalendar/core)

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.21
npm error Found: @fullcalendar/core@7.0.2
npm error node_modules/@fullcalendar/core
npm error   @fullcalendar/core@"7.0.2" from the root project
npm error   @fullcalendar/core@"7.0.2" from @fullcalendar/vue3@7.0.2
npm error   node_modules/@fullcalendar/vue3
npm error     @fullcalendar/vue3@"7.0.2" 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-08-29T14_55_06_055Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-29T14_55_06_055Z-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 from f43757c to cacd782 Compare August 26, 2026 10:51
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 cacd782 to 7ef7458 Compare August 29, 2026 14:55
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