renovate[bot]
commented
9 months 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 WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @sanity/portable-text-editor@3.18.1
npm WARN Found: styled-components@6.1.0
npm WARN node_modules/styled-components
npm WARN dev styled-components@"^6.1.0" from the root project
npm WARN 1 more (@sanity/ui)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer styled-components@"^5.2" from @sanity/portable-text-editor@3.18.1
npm WARN node_modules/@sanity/portable-text-editor
npm WARN @sanity/portable-text-editor@"3.18.1" from sanity@3.18.1
npm WARN node_modules/sanity
npm WARN
npm WARN Conflicting peer dependency: styled-components@5.3.11
npm WARN node_modules/styled-components
npm WARN peer styled-components@"^5.2" from @sanity/portable-text-editor@3.18.1
npm WARN node_modules/@sanity/portable-text-editor
npm WARN @sanity/portable-text-editor@"3.18.1" from sanity@3.18.1
npm WARN node_modules/sanity
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @sanity/semantic-release-preset@4.1.4
npm ERR! Found: semantic-release@22.0.5
npm ERR! node_modules/semantic-release
npm ERR! dev semantic-release@"^22.0.5" from the root project
npm ERR! peer semantic-release@">=18.0.0" from @semantic-release/changelog@6.0.3
npm ERR! node_modules/@semantic-release/changelog
npm ERR! @semantic-release/changelog@"6" from @sanity/semantic-release-preset@4.1.4
npm ERR! node_modules/@sanity/semantic-release-preset
npm ERR! dev @sanity/semantic-release-preset@"^4.1.4" from the root project
npm ERR! 6 more (@semantic-release/commit-analyzer, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@"20 || 21" from @sanity/semantic-release-preset@4.1.4
npm ERR! node_modules/@sanity/semantic-release-preset
npm ERR! dev @sanity/semantic-release-preset@"^4.1.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: semantic-release@21.1.2
npm ERR! node_modules/semantic-release
npm ERR! peer semantic-release@"20 || 21" from @sanity/semantic-release-preset@4.1.4
npm ERR! node_modules/@sanity/semantic-release-preset
npm ERR! dev @sanity/semantic-release-preset@"^4.1.4" 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!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-01T02_33_40_649Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-01T02_33_40_649Z-debug-0.log
This PR contains the following updates:
^10.0.0->^12.0.0Release Notes
lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)
### [`v12.0.0`](https://togithub.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-1200-2024-02-10) [Compare Source](https://togithub.com/lydell/eslint-plugin-simple-import-sort/compare/v11.0.0...v12.0.0) This release removes the support for import assignments added in version 11.0.0: - Turns out it was broken in some cases. - The suggested fix went past my complexity tolerance for such an esoteric feature. - I also learned that they aren’t really imports, and that I don’t understand their semantics well enough to know how sorting them affects your program. If you miss the support for import assignments, I suggest you write your own ESLint rule which moves them out of the way from the actual imports, sorting them or not. ### [`v11.0.0`](https://togithub.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-1100-2024-02-08) [Compare Source](https://togithub.com/lydell/eslint-plugin-simple-import-sort/compare/v10.0.0...v11.0.0) This release adds support for TypeScript import assignments (`import A = B.C` and `import A = require("module")`). Thanks to Szabolcs Kurdi ([@szku01](https://togithub.com/szku01)) and Svyatoslav Zaytsev ([@MillerSvt](https://togithub.com/MillerSvt))! It’s only a breaking change if you use TypeScript import assignments, and only in the form that you need to autofix your files. In other news, this release adds the `meta` plugin property in preparation for ESLint Flat Config, and avoids the deprecated `context.getSourceCode()` method (while still being backwards compatible).Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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 using a curated preset maintained by