Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency upgrades - non-major #476

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@next/eslint-plugin-next (source) 15.1.0 -> 15.1.2 age adoption passing confidence
@types/react (source) ^19.0.1 -> ^19.0.2 age adoption passing confidence
@types/react (source) 19.0.1 -> 19.0.2 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 8.18.0 -> 8.18.1 age adoption passing confidence
@typescript-eslint/parser (source) 8.18.0 -> 8.18.1 age adoption passing confidence
@typescript-eslint/utils (source) 8.18.0 -> 8.18.1 age adoption passing confidence
eslint (source) ^9.16.0 -> ^9.17.0 age adoption passing confidence
eslint (source) 9.16.0 -> 9.17.0 age adoption passing confidence
eslint-plugin-import-x 4.5.0 -> 4.6.1 age adoption passing confidence
eslint-plugin-react-x (source) 1.19.0 -> 1.20.1 age adoption passing confidence
globals ^15.13.0 -> ^15.14.0 age adoption passing confidence
next (source) 15.1.0 -> 15.1.2 age adoption passing confidence
stylelint (source) 16.11.0 -> 16.12.0 age adoption passing confidence

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v15.1.2

Compare Source

v15.1.1

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.18.1

Compare Source

🩹 Fixes
  • scope-manager: visit params decorator before nest scope (#​10475)
  • eslint-plugin: [no-unnecessary-condition] better message when comparing between literal types (#​10454)
  • eslint-plugin: use consistent naming for asserting types and casting values (#​10472)
  • eslint-plugin: [no-unnecessary-boolean-literal-compare] flag values of a type parameter with boolean type constraints (#​10474)
  • eslint-plugin: handle string like index type (#​10460)
  • eslint-plugin: [no-unnecessary-template-expression] don't report when an expression includes comment (#​10444)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.18.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/utils)

v8.18.1

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

eslint/eslint (eslint)

v9.17.0

Compare Source

un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

v4.6.1

Compare Source

Patch Changes

v4.6.0

Compare Source

Minor Changes
  • #​209 46d2360 Thanks @​SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue https://github.com/import-js/eslint-plugin-import/issues/1810.

    So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #​192.

    In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

    // eslint.config.js
    const eslintPluginImportX = require('eslint-plugin-import-x');
    const { createNodeResolver } = eslintPluginImportX;
    
    module.exports = {
      plugins: {
        'import-x': eslintPluginImportX,
      },
      settings: {
        'import-x/resolver-next': [
          // This is the new resolver we are introducing
          createNodeResolver({
            /**
             * The allowed extensions the resolver will attempt to find when resolving a module
             * By default it uses a relaxed extension list to search for both ESM and CJS modules
             * You can customize this list to fit your needs
             *
             * @​default ['.mjs', '.cjs', '.js', '.json', '.node']
             */
            extensions?: string[];
            /**
             * Optional, the import conditions the resolver will used when reading the exports map from "package.json"
             * By default it uses a relaxed condition list to search for both ESM and CJS modules
             * You can customize this list to fit your needs
             *
             * @​default ['default', 'module', 'import', 'require']
             */
            conditions: ['default', 'module', 'import', 'require'],
            // You can pass more options here, see the enhanced-resolve documentation for more details
            // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options
          }),
          // you can add more resolvers down below
          require('eslint-import-resolver-typescript').createTypeScriptImportResolver(
            /** options of eslint-import-resolver-typescript */
          )
        ],
      },
    };

    We do not plan to implement reading baseUrl and paths from the tsconfig.json file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered by enhanced-resolve), eslint-import-resolver-oxc (powered by oxc-resolver), eslint-import-resolver-next (also powered by oxc-resolver), or other similar resolvers.

Patch Changes

v4.5.1

Compare Source

Patch Changes
Rel1cx/eslint-react (eslint-plugin-react-x)

v1.20.1

Compare Source

🪄 Improvements

v1.20.0

Compare Source

✨ New
🪄 Improvements
sindresorhus/globals (globals)

v15.14.0

Compare Source

vercel/next.js (next)

v15.1.2

Compare Source

v15.1.1

Compare Source

stylelint/stylelint (stylelint)

v16.12.0

Compare Source

  • Added: selector-pseudo-class-allowed-list now checks @page pseudo-classes (#​8176) (@​Mouvedia).
  • Added: selector-pseudo-class-disallowed-list now checks @page pseudo-classes (#​8171) (@​Mouvedia).
  • Fixed: at-rule-property-required-list message to use "descriptor" for accuracy (#​8186) (@​ybiquitous).
  • Fixed: custom-property-no-missing-var-function false positives for container-name (#​8157) (@​Mouvedia).
  • Fixed: custom-property-no-missing-var-function false positives for custom properties passed to running() (#​8172) (@​Mouvedia).
  • Fixed: function-no-unknown false positives for running() (#​8172) (@​Mouvedia).
  • Fixed: selector-pseudo-class-no-unknown false positives for :open (#​8184) (@​lukewarlow).
  • Fixed: selector-pseudo-class-no-unknown false positives for :recto, :verso and :nth() (#​8170) (@​Mouvedia).
  • Fixed: selector-pseudo-class-no-unknown false positives for some moz-* vendor-prefixed pseudo-classes (#​8188) (@​Mouvedia).
  • Fixed: selector-pseudo-element-no-unknown false positives for ::details-content (#​8174) (@​lukewarlow).
  • Fixed: selector-type-no-unknown false positives for idents in functional pseudo-classes (#​8191) (@​elskhn).
  • Fixed: value-keyword-case false negatives (#​8158) (@​Mouvedia).
  • Fixed: value-keyword-case false positives for vendor-prefixed system colors (#​8146) (@​Mouvedia).

Configuration

📅 Schedule: Branch creation - "after 4pm on thursday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 enabled auto-merge (squash) December 19, 2024 16:16
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@renovate renovate bot merged commit 517f731 into main Dec 19, 2024
4 checks passed
@renovate renovate bot deleted the renovate/dependency-upgrades-non-major branch December 19, 2024 16:23
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.

0 participants