Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 21, 2025

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-check-file ^2.6.2 -> ^3.0.0 age confidence

Release Notes

dukeluo/eslint-plugin-check-file (eslint-plugin-check-file)

v3.3.1

Compare Source

Fixed
  • ignore dots inside brackets when extracting basename

v3.3.0

Compare Source

Added
  • add ignoreWords parameter to folder-naming-convention rule

v3.2.0

Compare Source

Added
  • add support for TypeScript declaration file

v3.1.0

Compare Source

Added
  • add support for css,json,markdown parsers
Changed
  • improve documentation

v3.0.0

Compare Source

Added
  • the plugin can lint non-js/ts files (e.g., images, styles, etc.) with processor eslint-processor-check-file
  • the rule filename-naming-convention can be used with a new built-in naming convention NEXT_JS_PAGE_ROUTER_FILENAME_CASE which is used for Next.js page router project
  • the rule no-index can set errorMessage property to customize the error message
  • the rule folder-match-with-fex can set errorMessage property to customize the error message
  • the rule folder-naming-convention can set errorMessage property to customize the error message
Changed
  • the error message of the rule folder-match-with-fex uses filename without path
  • improve documentation
Fixed
  • NEXT_JS_APP_ROUTER_CASE can support filename route like rss.xml
Removed
  • remove legacy support for context object
  • remove legacy support for rule filename-blocklist
  • remove legacy configuration support

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 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 Nov 21, 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: @openfeature/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^8.56.0" from the root project
npm error   dev eslint@"^8.57.0" from [email protected]
npm error   packages/angular
npm error     [email protected]
npm error     node_modules/angular
npm error       workspace packages/angular from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=9.0.0" from [email protected]
npm error node_modules/eslint-plugin-check-file
npm error   dev eslint-plugin-check-file@"^3.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-21T20_36_14_725Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-21T20_36_14_725Z-debug-0.log

@renovate renovate bot requested review from a team as code owners November 21, 2025 20:36
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