Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 25, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Change Age Confidence
@stylistic/eslint-plugin-js (source) ^2.6.1 -> ^4.0.0 age confidence
@stylistic/eslint-plugin-ts (source) ^2.6.1 -> ^4.0.0 age confidence

Release Notes

eslint-stylistic/eslint-stylistic (@​stylistic/eslint-plugin-js)

v4.4.1

Compare Source

Bug Fixes
  • keyword-spacing: check spaces around the type keyword in export declarations (#​797) (6854a3c)
Chores

v4.4.0

Compare Source

Features

v4.3.0

Compare Source

Features
Bug Fixes
  • eslint-plugin: only export interfaces in index (#​763) (93a4eb1)
  • handle new AST change on TSImportType (8f31461)
  • indent: handle ChainExpression and AwaitExpression when offsetTernaryExpressionsOffsetCallExpressions (#​751) (a1af663)
  • indent: wrong PropertyDefinition value offset when ts type have multiple line (#​774) (140e18f)
  • no-extra-parens: do not break specific ReturnStatement (#​738) (a375a92)
Documentation
Chores

v4.2.0

Compare Source

Features
  • config: update yield-star-spacing and generator-star-spacing config to align with Prettier (86d17c8)
Documentation

v4.1.0

Compare Source

Features
  • add module.exports named export for require(esm) compatibility (#​700) (668c955)
Documentation
Chores

v4.0.1

Compare Source

Bug Fixes
  • indent-binary-ops: handle { for left token check (#​693) (7f2740e)
Chores

v4.0.0

Compare Source

Features
Chores

v3.1.0

Compare Source

Features
  • generic-spacing: remove spaces in type param instantiation (#​677) (2a29e28)

v3.0.1

Compare Source

Bug Fixes

v3.0.0

Compare Source

⚠ BREAKING CHANGES
  • indent-binary-ops: remove unnecessary logic (#​645)
  • cross test function-call-spacing (#​565)
  • comma-style: turn off all exceptions option by default (#​602)
Features
  • comma-style: turn off all exceptions option by default (#​602) (c424d63)
  • cross test function-call-spacing (#​565) (80ec2e4)
  • quotes: Option to allow template literals only to avoid escape (#​643) (5558bdb)
  • type-generic-spacing: remove whitespaces in generic types (#​667) (8dd68e2)
Bug Fixes
  • jsx-wrap-multilines: prevent crash when using tabs (#​653) (8cbc9f8)
  • plus: dependencies bundle (ba9ed81)
Documentation
Chores

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 renovate bot force-pushed the renovate/major-eslint-stylistic-monorepo branch from c55cf68 to 068ac9f Compare February 10, 2025 04:56
@renovate renovate bot force-pushed the renovate/major-eslint-stylistic-monorepo branch from 068ac9f to a2f87c2 Compare February 18, 2025 11:48
@renovate renovate bot changed the title chore(deps): update eslint-stylistic monorepo to v3 (major) chore(deps): update eslint-stylistic monorepo to v4 (major) Feb 18, 2025
Copy link
Contributor Author

renovate bot commented Feb 18, 2025

⚠️ 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/eslint
npm error   dev eslint@"^8.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=9.0.0" from @stylistic/[email protected]
npm error node_modules/@stylistic/eslint-plugin-js
npm error   dev @stylistic/eslint-plugin-js@"^4.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-10-02T19_36_47_433Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-02T19_36_47_433Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-eslint-stylistic-monorepo branch from a2f87c2 to ab0e34d Compare August 10, 2025 12:28
@renovate renovate bot force-pushed the renovate/major-eslint-stylistic-monorepo branch from ab0e34d to ade68ae Compare August 31, 2025 10:10
@renovate renovate bot force-pushed the renovate/major-eslint-stylistic-monorepo branch from ade68ae to 7757a21 Compare October 2, 2025 19:36
@G-Rath G-Rath closed this Oct 2, 2025
Copy link
Contributor Author

renovate bot commented Oct 2, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-eslint-stylistic-monorepo branch October 2, 2025 19:41
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