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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update eslint rule and plugin updates #213

Merged
merged 3 commits into from
Dec 26, 2024
Merged

fix(deps): update eslint rule and plugin updates #213

merged 3 commits into from
Dec 26, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint-react/eslint-plugin (source) 1.17.1 -> 1.22.1 age adoption passing confidence
@stylistic/eslint-plugin (source) 2.11.0 -> 2.12.1 age adoption passing confidence
@typescript-eslint/parser (source) 8.16.0 -> 8.18.2 age adoption passing confidence
@typescript-eslint/rule-tester (source) 8.16.0 -> 8.18.2 age adoption passing confidence
@typescript-eslint/utils (source) 8.16.0 -> 8.18.2 age adoption passing confidence
eslint-import-resolver-typescript 3.6.3 -> 3.7.0 age adoption passing confidence
eslint-plugin-eslint-plugin 6.3.2 -> 6.4.0 age adoption passing confidence
eslint-plugin-import-x 4.4.3 -> 4.6.1 age adoption passing confidence
eslint-plugin-n 17.14.0 -> 17.15.1 age adoption passing confidence
eslint-plugin-react-hooks (source) 5.0.0 -> 5.1.0 age adoption passing confidence
typescript-eslint (source) 8.16.0 -> 8.18.2 age adoption passing confidence

Release Notes

Rel1cx/eslint-react (@​eslint-react/eslint-plugin)

v1.22.1

Compare Source

🪄 Improvements
  • docs: add getting started guides for JavaScript, TypeScript, and JavaScript with Babel.
  • docs: improve code samples in rules docs.
  • docs: improve eslint.config.js examples in README.md, docs and the examples folder.
  • docs: improve the error message and description of various rules.
  • refactor(website): better website layout and navigation experience.
📝 Changes in examples

The eslint.config.js in the examples now uses tsconfig's includes and excludes as the SSoT glob patterns for ESLint's files and ignores fields.

This approach can fundamentally avoid the errors[1, 2, 3] caused by mismatched config scopes between tsconfig.json and eslint.config.js.

v1.22.0

Compare Source

🪄 Improvements
  • refactor(plugins/x): rename jsx-use-vars to use-jsx-vars.
  • refactor(plugins/x): rename jsx-no-duplicate-props to no-duplicate-jsx-props.
  • refactor(plugins/dom): rename no-children-in-void-dom-elements to no-void-elements-with-children.
📝 Changes you should be aware of

The following rules have been renamed:

  • jsx-uses-vars to use-jsx-vars.
  • jsx-no-duplicate-props to no-duplicate-jsx-props.
  • dom/no-children-in-void-dom-elements to dom/no-void-elements-with-children.

The new rule names are aligned with the same rules in the biomejs/rules-sources/#eslint-plugin-react (if any) to enhance consistency. The old rule names will still be available until the next major update to avoid breaking changes.

v1.21.0

Compare Source

✨ New
  • feat(plugins/hooks-extra): add no-useless-custom-hooks rule by @​Rel1cx
🪄 Improvements
  • refactor(plugins/hooks-extra): deprecate rule no-redundant-custom-hook in favor of no-useless-custom-hooks (the previous rule will still be available until the next major update to avoid breaking changes).
📝 Changes in Rule implementation

no-useless-custom-hooks now detects Hook calls within comments and the following code no longer triggers a warning:

// ✅ Good: A Hook that will likely use some other Hooks later
function useAuth() {
  // TODO: Replace with this line when authentication is implemented:
  // return useContext(Auth);
  return TEST_USER;
}

v1.20.1

Compare Source

🪄 Improvements

v1.20.0

Compare Source

✨ New
🪄 Improvements

v1.19.0

Compare Source

✨ New
🪄 Improvements

v1.18.0

Compare Source

✨ New
🪄 Improvements
  • perf(plugins/dom): improve performance of no-children-in-void-dom-elements by @​Rel1cx

v1.17.3

Compare Source

🐞 Fixes
🪄 Improvements
  • Update @typescript-eslint's packages to ^8.17.0.

v1.17.2

Compare Source

🪄 Improvements
  • Update eslint's packages to ^9.16.0.
  • Update @typescript-eslint's packages to ^8.16.0.
  • Update ts-api-utils to ^2.0.0.
eslint-stylistic/eslint-stylistic (@​stylistic/eslint-plugin)

v2.12.1

Compare Source

Features
  • indent: introduce offsetTernaryExpressionsOffsetCallExpressions options (#​636) (c14a3ee)
Documentation
Chores

v2.12.0

Compare Source

Bug Fixes
  • comma-style: handles comma after default import and trailing comma (#​600) (2d8d8ce)
  • function-call-spacing: remove invalid defaults from schema (#​617) (0714754)
  • indent: consider CallExpression when offsetTernaryExpressions is true (#​625) (55d3529)
  • jsx-wrap-multilines: text between replacement texts included in parentheses (#​618) (0764252)
Documentation
Chores
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.18.2

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.

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.

v8.18.0

Compare Source

🩹 Fixes
❤️ Thank You
  • rtritto

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

v8.17.0

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/rule-tester)

v8.18.2

Compare Source

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

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

v8.18.1

Compare Source

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

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

v8.18.0

Compare Source

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

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

v8.17.0

Compare Source

This was a version bump only for rule-tester 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.2

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.

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.

v8.18.0

Compare Source

🩹 Fixes
❤️ Thank You
  • rtritto

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

v8.17.0

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.

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v3.7.0

Compare Source

Minor Changes

  • #​326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

    Previously

    // eslint.config.js
module.exports = {
  settings: {
    'import-x/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
      // or
      require.resolve('eslint-import-resolver-typescript'):
        alwaysTryTypes: true,
      }
    }
  }
}

    Now

    // eslint.config.js
const {
  createTypeScriptImportResolver,
} = require('eslint-import-resolver-typescript')

module.exports = {
  settings: {
    'import-x/resolver-next': [
      createTypeScriptImportResolver({
        alwaysTryTypes: true,
      }),
    ],
  },
}

    Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

eslint-community/eslint-plugin-eslint-plugin (eslint-plugin-eslint-plugin)

v6.4.0

Compare Source

Features
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

v4.5.0

Compare Source

Minor Changes
For eslint-plugin-import-x users

Like the ESLint flat config allows you to use js objects (e.g. import and require) as ESLint plugins, the new eslint-plugin-import-x resolver settings allow you to use js objects as custom resolvers through the new setting import-x/resolver-next:

// eslint.config.js
import { createTsResolver } from '#custom-resolver';
const { createOxcResolver } = require('path/to/a/custom/resolver');

const resolverInstance = new ResolverFactory({});
const customResolverObject = {
  interfaceVersion: 3,
  name: 'my-custom-eslint-import-resolver',
  resolve(modPath, sourcePath) {
    const path = resolverInstance.resolve(modPath, sourcePath);
    if (path) {
      return {
        found: true,
        path
      };
    }

    return {
      found: false,
      path: null
    }
  };
};

module.exports = {
  settings: {
    // multiple resolvers
    'import-x/resolver-next': [
      customResolverObject,
      createTsResolver(enhancedResolverOptions),
      createOxcResolver(oxcOptions),
    ],
    // single resolver:
    'import-x/resolver-next': [createOxcResolver(oxcOptions)]
  }
}

The new import-x/resolver-next no longer accepts strings as the resolver, thus will not be compatible with the ESLint legacy config (a.k.a. .eslintrc). Those who are still using the ESLint legacy config should stick with import-x/resolver.

In the next major version of eslint-plugin-import-x (v5), we will rename the currently existing import-x/resolver to import-x/resolver-legacy (which allows the existing ESLint legacy config users to use their existing resolver settings), and import-x/resolver-next will become the new import-x/resolver. When ESLint v9 (the last ESLint version with ESLint legacy config support) reaches EOL in the future, we will remove import-x/resolver-legacy.

We have also made a few breaking changes to the new resolver API design, so you can't use existing custom resolvers directly with import-x/resolver-next:

// When migrating to `import-x/resolver-next`, you CAN'T use legacy versions of resolvers directly:
module.exports = {
  settings: {
    // THIS WON'T WORK, the resolver interface required for `import-x/resolver-next` is different.
    'import-x/resolver-next': [
       require('eslint-import-resolver-node'),
       require('eslint-import-resolver-webpack'),
       require('some-custom-resolver')
    ];
  }
}

For easier migration, the PR also introduces a compat utility importXResolverCompat that you can use in your eslint.config.js:

// eslint.config.js
import eslintPluginImportX, { importXResolverCompat } from 'eslint-plugin-import-x';
// or
const eslintPluginImportX = require('eslint-plugin-import-x');
const { importXResolverCompat } = eslintPluginImportX;

module.exports = {
  settings: {
    // THIS WILL WORK as you have wrapped the previous version of resolvers with the `importXResolverCompat`
    'import-x/resolver-next': [
       importXResolverCompat(require('eslint-import-resolver-node'), nodeResolveOptions),
       importXResolverCompat(require('eslint-import-resolver-webpack'), webpackResolveOptions),
       importXResolverCompat(require('some-custom-resolver'), { option1: true, option2: '' })
    ];
  }
}
For custom import resolver developers

This is the new API design of the resolver interface:

export interface NewResolver {
  interfaceVersion: 3;
  name?: string; // This will be included in the debug log
  resolve: (modulePath: string, sourceFile: string) => ResolvedResult;
}

// The `ResultNotFound` (returned when not resolved) is the same, no changes
export interface ResultNotFound {
  found: false;
  path?: undefined;
}

// The `ResultFound` (returned resolve result) is also the same, no changes
export interface ResultFound {
  found: true;
  path: string | null;
}

export type ResolvedResult = ResultNotFound | ResultFound;

You will be able to import NewResolver from eslint-plugin-import-x/types.

The most notable change is that eslint-plugin-import-x no longer passes the third argument (options) to the resolve function.

We encourage custom resolvers' authors to consume the options outside the actual resolve function implementation. You can export a factory function to accept the options, this factory function will then be called inside the eslint.config.js to get the actual resolver:

// custom-resolver.js
exports.createCustomResolver = (options) => {
  // The options are consumed outside the `resolve` function.
  const resolverInstance = new ResolverFactory(options);

  return {
    name: 'custom-resolver',
    interfaceVersion: 3,
    resolve(mod, source) {
      const found = resolverInstance.resolve(mod, {});

      // Of course, you still have access to the `options` variable here inside
      // the `resolve` function. That's the power of JavaScript Closures~
    }
  }
};

// eslint.config.js
const { createCustomResolver } = require('custom-resolver')

module.exports = {
  settings: {
    'import-x/resolver-next': [
       createCustomResolver(options)
    ];
  }
}

This allows you to create a reusable resolver instance to improve the performance. With the existing version of the resolver interface, because the options are passed to the resolver function, you will have to create a resolver instance every time the resolve function is called:

module.exports = {
  interfaceVersion: 2,
  resolve(mod, source) {
    // every time the `resolve` function is called, a new instance is created
    // This is very slow
    const resolverInstance = ResolverFactory.createResolver({});
    const found = resolverInstance.resolve(mod, {});
  },
};

With the factory function pattern, you can create a resolver instance beforehand:

exports.createCustomResolver = (options) => {
  // `enhance-resolve` allows you to create a reusable instance:
  const resolverInstance = ResolverFactory.createResolver({});
  const resolverInstance = enhanceResolve.create({});

  // `oxc-resolver` also allows you to create a reusable instance:
  const resolverInstance = new ResolverFactory({});

  return {
    name: "custom-resolver",
    interfaceVersion: 3,
    resolve(mod, source) {
      // the same re-usable instance is shared across `resolve` invocations.
      // more performant
      const found = resolverInstance.resolve(mod, {});
    },
  };
};
Patch Changes
eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.15.1

Compare Source

🩹 Fixes
  • Promise.withResolvers is supported since node 22.11 (#​398) (c5bcb3a)

v17.15.0

Compare Source

🌟 Features
🩹 Fixes
  • no-unsupported: Correctly handle recursive objects on a per module basis (#​396) (db384d1)
facebook/react (eslint-plugin-react-hooks)

v5.1.0

Compare Source

typescript-eslint/typescript-eslint (typescript-eslint)

v8.18.2

Compare Source

🩹 Fixes
  • typescript-eslint: export types so that declarations can be named for dts files (#​10513)
❤️ Thank You

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

v8.18.1

Compare Source

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

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

v8.18.0

Compare Source

🩹 Fixes
❤️ Thank You
  • rtritto

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

v8.17.0

Compare Source

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

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

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.

👻 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 added the renovate label Dec 1, 2024
@renovate renovate bot requested a review from frantic1048 December 1, 2024 13:12
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 63edfff to fbc2ffa Compare December 1, 2024 13:13
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from fbc2ffa to d370a72 Compare December 2, 2024 19:00
@renovate renovate bot changed the title fix(deps): update dependency @eslint-react/eslint-plugin to v1.17.2 fix(deps): update eslint rule and plugin updates Dec 2, 2024
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from d370a72 to 8bfa1fb Compare December 2, 2024 19:01
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 8bfa1fb to 9926b7c Compare December 2, 2024 21:09
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 9926b7c to f826511 Compare December 2, 2024 21:10
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from f826511 to f75f7ad Compare December 3, 2024 10:33
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from f75f7ad to 339eb46 Compare December 3, 2024 10:33
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 339eb46 to 921fea7 Compare December 3, 2024 16:32
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 921fea7 to 9c6a5aa Compare December 3, 2024 16:32
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 9c6a5aa to ba7d18d Compare December 5, 2024 19:52
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from ba7d18d to 03aa0d8 Compare December 5, 2024 19:53
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 03aa0d8 to 208860b Compare December 7, 2024 21:02
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 208860b to 15983b7 Compare December 7, 2024 21:03
@renovate renovate bot changed the title fix(deps): update eslint rule and plugin updates fix(deps): update eslint rule and plugin updates - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/eslint-rule-and-plugin-updates branch December 8, 2024 18:37
@renovate renovate bot changed the title fix(deps): update eslint rule and plugin updates - autoclosed fix(deps): update eslint rule and plugin updates Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch 2 times, most recently from 15983b7 to 72fd8a7 Compare December 9, 2024 01:53
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 72fd8a7 to 98d0d1b Compare December 9, 2024 01:54
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 98d0d1b to 372b368 Compare December 9, 2024 05:49
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 372b368 to 8a2cb26 Compare December 9, 2024 05:50
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 8a2cb26 to b199a37 Compare December 9, 2024 17:50
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from b199a37 to 731ba98 Compare December 9, 2024 17:51
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 731ba98 to 3727413 Compare December 10, 2024 01:23
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 2983522 to 8657572 Compare December 17, 2024 06:33
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 8657572 to bc02316 Compare December 17, 2024 07:04
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from bc02316 to d82b577 Compare December 17, 2024 07:05
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from d82b577 to 81330d0 Compare December 17, 2024 13:51
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 81330d0 to 0bee7d8 Compare December 17, 2024 13:52
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 0bee7d8 to ee22bf8 Compare December 18, 2024 05:27
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from ee22bf8 to d8b83fe Compare December 18, 2024 05:28
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from d8b83fe to b315763 Compare December 18, 2024 09:35
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from b315763 to b61b9cb Compare December 18, 2024 09:36
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from b61b9cb to c525e8f Compare December 19, 2024 08:50
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from c525e8f to 74c022c Compare December 19, 2024 08:51
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 74c022c to f0ce453 Compare December 19, 2024 15:24
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from f0ce453 to 38f50a1 Compare December 19, 2024 15:25
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 38f50a1 to 9d9a90c Compare December 20, 2024 05:27
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 9d9a90c to b8be5b6 Compare December 20, 2024 05:28
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from b8be5b6 to 044c06a Compare December 20, 2024 10:57
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 044c06a to b67f829 Compare December 20, 2024 10:58
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from b67f829 to 4128ee2 Compare December 22, 2024 00:34
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 4128ee2 to 788f6ee Compare December 22, 2024 00:35
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 788f6ee to 063b448 Compare December 23, 2024 01:44
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 063b448 to 8f74442 Compare December 23, 2024 01:45
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from 8f74442 to 14b8e48 Compare December 23, 2024 20:26
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from 14b8e48 to a11c786 Compare December 23, 2024 20:27
@renovate renovate bot force-pushed the renovate/eslint-rule-and-plugin-updates branch from a11c786 to a7c6746 Compare December 23, 2024 21:51
@rainx rainx force-pushed the renovate/eslint-rule-and-plugin-updates branch from a7c6746 to b4b6392 Compare December 23, 2024 21:52
@frantic1048 frantic1048 merged commit 93d81d7 into main Dec 26, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@frantic1048 frantic1048 frantic1048 approved these changes

Assignees

@frantic1048 frantic1048

Labels
renovate
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@frantic1048