chore(deps): update dependency stylelint to v15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
stylelint (source)	^14.9.1 -> ^15.0.0

---

Release Notes

stylelint/stylelint

v15.0.0

Compare Source

Migrating to 15.0.0 guide.

• Removed: Node.js 12 support (#​6477) (@​ybiquitous). (BREAKING)
• Removed: support for processors (#​6479) (@​ybiquitous). (BREAKING)
• Removed: syntax option (#​6420) (@​fpetrakov). (BREAKING)
• Changed: extends in overrides to merge to be consistent with plugins behaviour (#​6380) (@​jasikpark). (BREAKING)
• Changed: type definitions to reorganize (#​6510) (@​ybiquitous). (BREAKING)
• Changed: type names to be more consistent (#​6503) (@​ybiquitous). (BREAKING)
• Deprecated: stylistic rules handled by Prettier (#​6504) (@​ybiquitous).
• Added: declaration-property-value-no-unknown rule (#​6511) (@​jeddy3).
• Added: media-feature-name-unit-allowed-list rule (#​6550) (@​mattxwang).
• Added: function-url-quotes autofix (#​6558) (@​mattxwang).
• Added: ignore: ["custom-elements"] to selector-max-type (#​6588) (@​muddv).
• Added: ignoreFunctions: [] to unit-disallowed-list (#​6592) (@​mattxwang).
• Added: deprecated rule warnings (#​6561) (@​ybiquitous).
• Added: message arguments to declaration-property-unit-allowed-list (#​6570) (@​mattxwang).
• Fixed: overrides.files in config to allow basename glob patterns (#​6547) (@​ybiquitous).
• Fixed: at-rule-no-unknown false positives for @scroll-timeline (#​6554) (@​mattxwang).
• Fixed: function-no-unknown false positives for interpolation and backticks in CSS-in-JS (#​6565) (@​hudochenkov).
• Fixed: keyframe-selector-notation false positives for named timeline ranges (#​6605) (@​kimulaco).
• Fixed: property-no-unknown false negatives for newer custom syntaxes (#​6553) (@​43081j).
• Fixed: selector-attribute-quotes false positives for "never" (#​6571) (@​mattxwang).
• Fixed: selector-not-notation autofix for "simple" option (#​6608) (@​Mouvedia).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 WARN ERESOLVE overriding peer dependency
npm WARN While resolving: stylelint-config-recommended@6.0.0
npm WARN Found: stylelint@15.0.0
npm WARN node_modules/stylelint
npm WARN   dev stylelint@"^15.0.0" from the root project
npm WARN   2 more (stylelint-config-html, stylelint-config-recommended-vue)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer stylelint@"^14.0.0" from stylelint-config-recommended@6.0.0
npm WARN node_modules/stylelint-config-recommended
npm WARN   stylelint-config-recommended@">=6.0.0" from stylelint-config-recommended-vue@1.1.0
npm WARN   node_modules/stylelint-config-recommended-vue
npm WARN 
npm WARN Conflicting peer dependency: stylelint@14.16.1
npm WARN node_modules/stylelint
npm WARN   peer stylelint@"^14.0.0" from stylelint-config-recommended@6.0.0
npm WARN   node_modules/stylelint-config-recommended
npm WARN     stylelint-config-recommended@">=6.0.0" from stylelint-config-recommended-vue@1.1.0
npm WARN     node_modules/stylelint-config-recommended-vue
npm notice 
npm notice New major version of npm available! 8.19.3 -> 9.4.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.4.2>
npm notice Run `npm install -g npm@9.4.2` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: stylelint-config-standard@29.0.0
npm ERR! Found: stylelint@15.0.0
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"^15.0.0" from the root project
npm ERR!   peer stylelint@">=14.0.0" from stylelint-config-html@1.0.0
npm ERR!   node_modules/stylelint-config-html
npm ERR!     stylelint-config-html@">=1.0.0" from stylelint-config-recommended-vue@1.1.0
npm ERR!     node_modules/stylelint-config-recommended-vue
npm ERR!       dev stylelint-config-recommended-vue@"^1.1.0" from the root project
npm ERR!     stylelint-config-html@"^1.0.0" from stylelint-stylus@0.17.0
npm ERR!     node_modules/stylelint-stylus
npm ERR!       dev stylelint-stylus@"^0.17.0" from the root project
npm ERR!   1 more (stylelint-config-recommended-vue)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^14.14.0" from stylelint-config-standard@29.0.0
npm ERR! node_modules/stylelint-config-standard
npm ERR!   dev stylelint-config-standard@"^29.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: stylelint@14.16.1
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@"^14.14.0" from stylelint-config-standard@29.0.0
npm ERR!   node_modules/stylelint-config-standard
npm ERR!     dev stylelint-config-standard@"^29.0.0" 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/renovate-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/renovate-cache/others/npm/_logs/2023-02-09T22_50_46_978Z-debug-0.log

[changeset-bot]

⚠️ No Changeset found

Latest commit: 91e1175

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR