Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2023

This PR contains the following updates:

Package Change Age Confidence
stylelint-prettier ^1.1.2 -> ^5.0.0 age confidence

Release Notes

prettier/stylelint-prettier (stylelint-prettier)

v5.0.3

Compare Source

Avoid deprecation warning when encountering parsing errors in Stylelint >=16.13.0 (#​385)

v5.0.2

Compare Source

Fix case where less files were incorrectly mangled when using v5.0.1 (#​363)

v5.0.1

Compare Source

Fix case where when autofixing multiple other rules in addition to prettier, the other autofixes would be thrown away (#​360)

v5.0.0

Compare Source

Increase the minimum required versions of stylelintand node. Stylelint v16
has converted its codebase to esm and has deprecated its commonjs apis. We've followed their suggested migration guide and stylelint-prettier is now an esm-only package. This has required dropping support for v15 at the same time.

  • Minimum stylelint version is now v16 (drop support for v15.x)
  • Minimum node requirements is now >=18.12.0 (drop support for v14.x and v16.x)

v4.1.0

Compare Source

  • Added end indexes for violations - the squiggly line in vscode will now cover more than one character. (#​341)
  • Do not trigger prettier for .astro files. (#​340)

v4.0.2

Compare Source

Fix case where an error is thrown when no prettier configuration file is found (#​311)

v4.0.1

Compare Source

Fix prettier-plugin-svelte support by ensuring .svelte files are ignored. The regression of them not being ignored only affected v4.0.0. (#​309)

v4.0.0

Compare Source

Add support for Prettier v3.

In order to make Prettier v3 work, we've had to drop support for Prettier v2.x and Stylelint less that v15.8.0. Maintaining temporary support for Prettier v2 and v3 at the same time isn't worth the complication that results thanks to prettier's migration to es modules. When you update to prettier v3, ensure that you update stylelint-prettier at the same time.

  • Minimum supported prettier version is now v3.0.0.
  • Minimum supported stylelint version is now v15.8.0.

v3.0.0

Compare Source

Remove stylelint-config-prettier from the recommended config. Stylelint v15 deprecated the rules that stylelint-config-prettier disabled, thus if you do not use those deprecated rules then you do not need stylelint-config-prettier. If you are still using these deprecated rules then you should install and configure stylelint-config-prettier separately.

Increase the mimimum required node version. No code changes have been required and v2.0.0 works with stylelint v15, however continuing to test with the unsupported node 12 is a burden that is not worth carrying.

  • Minimum node requirement is now "^14.17.0 || >=16.0.0" (drop support for v12.x)
  • If you extended from the stylelint-prettier/recommended in v2 then you must add an explict extend from stylelint-config-prettier to retain the same behaviour.

v2.0.0

Compare Source

Increase the minimum required versions of stylelint, prettier and node. No code changes have been required and v1.2.0 works with stylelint v14, however continuing to test old these old unsupported versions is getting more difficult thanks to internal API changes. (#​198)

  • Minimum stylelint version is now v14 (drop support for v9.5 through v13.x)
  • Minimum prettier version is now v2 (drop support for v1.x)
  • Minimum node requirements is now ^12.22.0 || ^14.17.0 || >=16.0.0 (drop support for v8.x and v10.x)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 12, 2023

⚠ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/prettier
npm ERR!   dev prettier@"^2.0.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@">=3.0.0" from [email protected]
npm ERR! node_modules/stylelint-prettier
npm ERR!   dev stylelint-prettier@"^5.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-12T05_53_59_337Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-12T05_53_59_337Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency stylelint-prettier to v5 chore(deps): update dependency stylelint-prettier to v5 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/stylelint-prettier-5.x branch December 8, 2024 18:49
@renovate renovate bot changed the title chore(deps): update dependency stylelint-prettier to v5 - autoclosed chore(deps): update dependency stylelint-prettier to v5 Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/stylelint-prettier-5.x branch from 4138504 to f8f0512 Compare December 9, 2024 01:58
@renovate
Copy link
Contributor Author

renovate bot commented Dec 9, 2024

⚠️ 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 Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/prettier
npm error   dev prettier@"^2.0.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer prettier@">=3.0.0" from [email protected]
npm error node_modules/stylelint-prettier
npm error   dev stylelint-prettier@"^5.0.0" 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-11-02T11_31_21_295Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-02T11_31_21_295Z-debug-0.log

@renovate renovate bot force-pushed the renovate/stylelint-prettier-5.x branch from f8f0512 to cd893b0 Compare July 27, 2025 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant