Skip to content

fix(deps): update fullcalendar monorepo to v7 - #63

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

fix(deps): update fullcalendar monorepo to v7#63
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-fullcalendar-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 19, 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/icalendar (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: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 commented Jul 19, 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: @fullcalendar/daygrid@6.1.21
npm warn Found: @fullcalendar/core@7.0.2
npm warn node_modules/@fullcalendar/core
npm warn   @fullcalendar/core@"7.0.2" from the root project
npm warn   2 more (@fullcalendar/icalendar, @fullcalendar/vue3)
npm warn
npm warn Could not resolve dependency:
npm warn peer @fullcalendar/core@"~6.1.21" from @fullcalendar/daygrid@6.1.21
npm warn node_modules/@fullcalendar/daygrid
npm warn   @fullcalendar/daygrid@"~6.1.21" from @fullcalendar/timegrid@6.1.21
npm warn   node_modules/@fullcalendar/timegrid
npm warn
npm warn Conflicting peer dependency: @fullcalendar/core@6.1.21
npm warn node_modules/@fullcalendar/core
npm warn   peer @fullcalendar/core@"~6.1.21" from @fullcalendar/daygrid@6.1.21
npm warn   node_modules/@fullcalendar/daygrid
npm warn     @fullcalendar/daygrid@"~6.1.21" from @fullcalendar/timegrid@6.1.21
npm warn     node_modules/@fullcalendar/timegrid
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @fullcalendar/interaction@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/icalendar@7.0.2
npm error   node_modules/@fullcalendar/icalendar
npm error     @fullcalendar/icalendar@"7.0.2" from the root project
npm error   1 more (@fullcalendar/vue3)
npm error
npm error Could not resolve dependency:
npm error peer @fullcalendar/core@"~6.1.21" from @fullcalendar/interaction@6.1.21
npm error node_modules/@fullcalendar/interaction
npm error   @fullcalendar/interaction@"6.1.21" from the root project
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/interaction@6.1.21
npm error   node_modules/@fullcalendar/interaction
npm error     @fullcalendar/interaction@"6.1.21" from the root project
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-07-30T17_48_09_378Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-30T17_48_09_378Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-fullcalendar-monorepo branch 3 times, most recently from c1eeec1 to ec19fe7 Compare July 27, 2026 01:05
@renovate
renovate Bot force-pushed the renovate/major-fullcalendar-monorepo branch from ec19fe7 to 5b9047a Compare July 30, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants