renovate[bot]
commented
1 month ago β οΈ 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 could not resolve
npm error
npm error While resolving: @nextcloud/calendar-availability-vue@2.2.1
npm error Found: @nextcloud/l10n@3.1.0
npm error node_modules/@nextcloud/l10n
npm error @nextcloud/l10n@"^3.1.0" from the root project
npm error @nextcloud/l10n@"^3.0.1" from @nextcloud/vue@8.12.0
npm error node_modules/@nextcloud/vue
npm error @nextcloud/vue@"^8.12.0" from the root project
npm error peer @nextcloud/vue@"^8.6.2" from @nextcloud/calendar-availability-vue@2.2.1
npm error node_modules/@nextcloud/calendar-availability-vue
npm error @nextcloud/calendar-availability-vue@"^2.2.1" from the root project
npm error 1 more (@nextcloud/dialogs)
npm error
npm error Could not resolve dependency:
npm error peer @nextcloud/l10n@"^1.4 || ^2.0" from @nextcloud/calendar-availability-vue@2.2.1
npm error node_modules/@nextcloud/calendar-availability-vue
npm error @nextcloud/calendar-availability-vue@"^2.2.1" from the root project
npm error
npm error Conflicting peer dependency: @nextcloud/l10n@1.6.0
npm error node_modules/@nextcloud/l10n
npm error peer @nextcloud/l10n@"^1.4 || ^2.0" from @nextcloud/calendar-availability-vue@2.2.1
npm error node_modules/@nextcloud/calendar-availability-vue
npm error @nextcloud/calendar-availability-vue@"^2.2.1" 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 /tmp/renovate/cache/others/npm/_logs/2024-06-04T22_42_56_005Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-04T22_42_56_005Z-debug-0.log
codecov[bot]
st3iny
This PR contains the following updates:
^2.2.0->^3.1.0Release Notes
nextcloud-libraries/nextcloud-l10n (@nextcloud/l10n)
### [`v3.1.0`](https://togithub.com/nextcloud-libraries/nextcloud-l10n/blob/HEAD/CHANGELOG.md#310---2024-05-07) [Compare Source](https://togithub.com/nextcloud-libraries/nextcloud-l10n/compare/v3.0.1...v3.1.0) ##### Added - Allow setting `escape` option per parameter replacing.\ For more security this should be used instead of disabling paramter escaping, see [pull request #756](https://togithub.com/nextcloud-libraries/nextcloud-l10n/pull/756) ```js // Example t( 'my-app', '{a}{userInput}{a_end}', { a: { value: '', escape: false, }, userInput: somePossiblyInsecureValue, // This will be escaped a_end: { value: '', escape: false, } }, ) ``` ### [`v3.0.1`](https://togithub.com/nextcloud-libraries/nextcloud-l10n/blob/HEAD/CHANGELOG.md#301---2024-05-04) [Compare Source](https://togithub.com/nextcloud-libraries/nextcloud-l10n/compare/v3.0.0...v3.0.1) ##### Fixed - Ensure that built type definitions are bundled with the release and located in the correct directory ### [`v3.0.0`](https://togithub.com/nextcloud-libraries/nextcloud-l10n/blob/HEAD/CHANGELOG.md#300---2024-05-02) [Compare Source](https://togithub.com/nextcloud-libraries/nextcloud-l10n/compare/v2.2.0...v3.0.0) [Full Changelog](https://togithub.com/nextcloud-libraries/nextcloud-l10n/compare/v2.2.0...v3.0.0) ##### Breaking changes Instead of also sanitizing the replacing variables, now only the result is sanitized, see [pull request #648](https://togithub.com/nextcloud-libraries/nextcloud-l10n/pull/648). This will improve the performance if multiple placeholders are used and it allows this, while the string is still sanitized: ```js t( 'See {linkstart}documentation{linkend}', { linkstart: '', linkend: '', }, // No number undefined, { // Do not escape the result as we want the HTML anchor element escape: false, } ) ``` ##### Added - feat: export aliases `t` and `n` for `translate` and `translatePlural` ##### Fixed - fix!: Only sanitize the result string when replacing variables ##### Changed - Update NPM to latest LTS v10 - Migrate to vite for transpiling and vitest for testing - chore: Added more tests for special cases on plural forms - chore(deps): Bump tough-cookie to 4.1.3 - chore(deps): Bump postcss to 8.4.31 - chore(deps): Bump [@nextcloud/typings](https://togithub.com/nextcloud/typings) to 1.8.0 - chore(deps): Bump dompurify to 3.1.1 - chore(deps): Bump [@nextcloud/router](https://togithub.com/nextcloud/router) to 3.0.1Configuration
π 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.
This PR has been generated by Mend Renovate. View repository job log here.