fix(deps): bump @nextcloud/calendar-js from 8.1.4 to ^8.1.6 (main)
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| @nextcloud/calendar-js | ^8.1.4 -> ^8.1.6 |
[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
nextcloud/calendar-js (@nextcloud/calendar-js)
v8.1.6
Bug Fixes
- time frame check of vtodos (8f900ce)
v8.1.5
Bug Fixes
Configuration
📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, 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 this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠️ 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @nextcloud/[email protected]
npm error node_modules/@nextcloud/timezones
npm error @nextcloud/timezones@"^0.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @nextcloud/timezones@"^1.0.0" from @nextcloud/[email protected]
npm error node_modules/@nextcloud/calendar-js
npm error @nextcloud/calendar-js@"^8.1.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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/2025-12-03T16_31_06_835Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-03T16_31_06_835Z-debug-0.log