fix(deps): bump @fullcalendar/multimonth from 6.1.8 to v6.1.9 (main) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@fullcalendar/multimonth (source)	6.1.8 -> 6.1.9

---

Release Notes

fullcalendar/fullcalendar (@​fullcalendar/multimonth)

v6.1.9

Compare Source

• fix: Table selection is not prevented when long pressing to drag events in Safari (#​7441)
• fix: Custom event rendering with white-space:normal can causes infinite loop (#​7447)
• fix: eventClick does not fire for allDay events with async provided resources (#​7365)
• fix: eventContent with Preact nodes (via createElement) not rendering (#​7342)
• fix: React 16: calling calendarApi methods within useEffect causes fatal error (#​7448)
• fix: Angular/Vue2: dot-event element from eventDidMount does not exists in the DOM (#​7191)
• fix: Angular Universal: document is not defined error (#​7352)

---

Configuration

📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

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

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: calendar@4.6.0-alpha.1
npm ERR! Found: @fullcalendar/core@6.1.8
npm ERR! node_modules/@fullcalendar/core
npm ERR!   @fullcalendar/core@"6.1.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @fullcalendar/core@"~6.1.9" from @fullcalendar/multimonth@6.1.9
npm ERR! node_modules/@fullcalendar/multimonth
npm ERR!   @fullcalendar/multimonth@"6.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/04c479/c61802/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/04c479/c61802/cache/others/npm/_logs/2023-09-27T01_54_55_205Z-debug-0.log

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (7279bfc) 22.59% compared to head (4fbb032) 64.26%.
Report is 2 commits behind head on main.

Additional details and impacted files

@@              Coverage Diff              @@
##               main    #5492       +/-   ##
=============================================
+ Coverage     22.59%   64.26%   +41.66%     
  Complexity      395      395               
=============================================
  Files           241       39      -202     
  Lines         11854     2065     -9789     
  Branches       2306        0     -2306     
=============================================
- Hits           2679     1327     -1352     
+ Misses         9175      738     -8437     

Flag	Coverage Δ
javascript	?
php	64.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 202 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.