renovate[bot]
commented
1 year ago Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
This PR contains the following updates:
4.3.5->4.3.618.17.12->18.17.146.5.0->6.6.06.5.0->6.6.0v3.6.0->v4.0.046.5.0->46.5.13.12.0->3.12.10.35.0->0.36.020.5.1->20.6.0Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v6.6.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#660-2023-09-04) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.5.0...v6.6.0) ##### Bug Fixes - **eslint-plugin:** \[key-spacing] consider properties with parens and comments ([#7525](https://togithub.com/typescript-eslint/typescript-eslint/issues/7525)) ([7012279](https://togithub.com/typescript-eslint/typescript-eslint/commit/7012279b8510f9fcaee64b610d0a66e8e90f0865)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v6.6.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#660-2023-09-04) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.5.0...v6.6.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.actions/checkout (actions/checkout)
### [`v4.0.0`](https://togithub.com/actions/checkout/blob/HEAD/CHANGELOG.md#v400) [Compare Source](https://togithub.com/actions/checkout/compare/v3.6.0...v4.0.0) - [Support fetching without the --progress option](https://togithub.com/actions/checkout/pull/1067) - [Update to node20](https://togithub.com/actions/checkout/pull/1436)gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)
### [`v46.5.1`](https://togithub.com/gajus/eslint-plugin-jsdoc/releases/tag/v46.5.1) [Compare Source](https://togithub.com/gajus/eslint-plugin-jsdoc/compare/v46.5.0...v46.5.1) ##### Bug Fixes - revert use of too-high language feature; fixes [#1148](https://togithub.com/gajus/eslint-plugin-jsdoc/issues/1148) ([85a21bf](https://togithub.com/gajus/eslint-plugin-jsdoc/commit/85a21bfb696feace06da1a4e76977bcf34a9c45c))dubzzz/fast-check (fast-check)
### [`v3.12.1`](https://togithub.com/dubzzz/fast-check/blob/HEAD/packages/fast-check/CHANGELOG.md#3121) [Compare Source](https://togithub.com/dubzzz/fast-check/compare/v3.12.0...v3.12.1) *Better support for types on ESM targets* \[[Code](https://togithub.com/dubzzz/fast-check/tree/v3.12.1)]\[[Diff](https://togithub.com/dubzzz/fast-check/compare/v3.12.0...v3.12.1)] #### Fixes - ([PR#4172](https://togithub.com/dubzzz/fast-check/pull/4172)) Bug: Better declare ESM's types - ([PR#4177](https://togithub.com/dubzzz/fast-check/pull/4177)) Bug: Replace macros in published esm types - ([PR#4156](https://togithub.com/dubzzz/fast-check/pull/4156)) CI: Stop formatting built website - ([PR#4155](https://togithub.com/dubzzz/fast-check/pull/4155)) CI: Add TypeScript checks on website - ([PR#4171](https://togithub.com/dubzzz/fast-check/pull/4171)) CI: Update Devcontainer settings - ([PR#4181](https://togithub.com/dubzzz/fast-check/pull/4181)) CI: Add exempted labels for stale bot - ([PR#4136](https://togithub.com/dubzzz/fast-check/pull/4136)) Clean: Drop dependency [@testing-library/jest-dom](https://togithub.com/testing-library/jest-dom) - ([PR#4107](https://togithub.com/dubzzz/fast-check/pull/4107)) Doc: What's new article for fast-check 3.12.0 - ([PR#4118](https://togithub.com/dubzzz/fast-check/pull/4118)) Doc: Drop raw bench results from release note - ([PR#4117](https://togithub.com/dubzzz/fast-check/pull/4117)) Test: Stabilize test related to NaN in exclusive mode - ([PR#4033](https://togithub.com/dubzzz/fast-check/pull/4033)) Tooling: Update formattingigorshubovych/markdownlint-cli (markdownlint-cli)
### [`v0.36.0`](https://togithub.com/igorshubovych/markdownlint-cli/releases/tag/v0.36.0): 0.36.0 [Compare Source](https://togithub.com/igorshubovych/markdownlint-cli/compare/v0.35.0...v0.36.0) - Update `markdownlint` dependency to `0.30.0` - Use `micromark` in MD022/MD026/MD032/MD037/MD045/MD051 - Incorporate `micromark-extension-math` for math syntax - Allow custom rules to override information URL - Update all dependencies via `Dependabot`nodejs/node (node)
### [`v20.6.0`](https://togithub.com/nodejs/node/releases/tag/v20.6.0): 2023-09-04, Version 20.6.0 (Current), @juanarbol prepared by @UlisesGascon [Compare Source](https://togithub.com/nodejs/node/compare/v20.5.1...v20.6.0) ##### Notable changes ##### built-in `.env` file support Starting from Node.js v20.6.0, Node.js supports `.env` files for configuring environment variables. Your configuration file should follow the INI file format, with each line containing a key-value pair for an environment variable. To initialize your Node.js application with predefined configurations, use the following CLI command: `node --env-file=config.env index.js`. For example, you can access the following environment variable using `process.env.PASSWORD` when your application is initialized: ```text PASSWORD=nodejs ``` In addition to environment variables, this change allows you to define your `NODE_OPTIONS` directly in the `.env` file, eliminating the need to include it in your `package.json`. This feature was contributed by Yagiz Nizipli in [#48890](https://togithub.com/nodejs/node/pull/48890). ##### `import.meta.resolve` unflagged In ES modules, [`import.meta.resolve(specifier)`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import.meta/resolve) can be used to get an absolute URL string to which `specifier` resolves, similar to `require.resolve` in CommonJS. This aligns Node.js with browsers and other server-side runtimes. This feature was contributed by Guy Bedford in [#49028](https://togithub.com/nodejs/node/pull/49028) ##### New `node:module` API `register` for module customization hooks; new `initialize` hook There is a new API `register` available on `node:module` to specify a file that exports module customization hooks, and pass data to the hooks, and establish communication channels with them. The “define the file with the hooks” part was previously handled by a flag `--experimental-loader`, but when the hooks moved into a dedicated thread in 20.0.0 there was a need to provide a way to communicate between the main (application) thread and the hooks thread. This can now be done by calling `register` from the main thread and passing data, including `MessageChannel` instances. We encourage users to migrate to an approach that uses [`--import`](https://nodejs.org/api/cli.html#--importmodule) with `register`, such as: ```bash node --import ./file-that-calls-register.js ./app.js ``` Using `--import` ensures that the customization hooks are registered before any application code runs, even the entry point. This feature was contributed by Izaak Schroeder in [#48842](https://togithub.com/nodejs/node/pull/48842) and [#48559](https://togithub.com/nodejs/node/pull/48559) ##### Module customization `load` hook can now support CommonJS Authors of module customization hooks can how handle both ES module and CommonJS sources in the `load` hook. This works for CommonJS modules referenced via either `import` or `require`, so long as [the main entry point of the application is handled by the ES module loader](https://nodejs.org/api/cli.html#program-entry-point) (such as because the entry point is an ES module file, or if the `--import` flag is passed). This should simplify the customization of the Node.js module loading process, as package authors can customize more of Node.js without relying on deprecated APIs such as `require.extensions`. This feature was contributed by Antoine du Hamel in [#47999](https://togithub.com/nodejs/node/pull/47999) ##### Node.js C++ addons now have experimental support for cppgc (Oilpan), a C++ garbage collection library in V8. Now when Node.js starts up, it makes sure that there is a `v8::CppHeap` attached to the V8 isolate. This enables users to allocate in the `v8::CppHeap` using `Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.