Use ember-estree, remove babel #566
Annotations
38 errors and 34 warnings
|
TS: 5.6, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.3, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.4, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: rc, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: next, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: 5.7, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: next, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.4, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.6, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: 5.3, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: 5.3, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.7, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.5, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.5, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.3, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: 5.6, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: 5.6, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: rc, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: 5.4, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: 5.7, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.5, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: rc, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.5, eslint-ts-deps: canary
Process completed with exit code 1.
|
|
TS: 5.4, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: next, eslint-ts-deps: ^8
Process completed with exit code 1.
|
|
TS: 5.7, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
TS: rc, eslint-ts-deps: ^6
Process completed with exit code 1.
|
|
TS: next, eslint-ts-deps: ^7
Process completed with exit code 1.
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid >
<template>
<Foo />
<Bar>
<div></div>
</Bar>
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L514
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of 2 but got 1
- Expected
+ Received
- 2
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:514:30
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid >
<template>
{{#let 'x' as |noop usedEl notUsed|}}
{{noop}}
<usedEl />
<undef.x />
{{/let}}
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L514
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of 2 but got 1
- Expected
+ Received
- 2
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:514:30
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid >
<template>
{{noop}}
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L525
AssertionError: expected 'message: Parsing error: Cannot read p…' to strictly equal 'message: \'noop\' is not defined.'
Expected: "message: 'noop' is not defined."
Received: "message: Parsing error: Cannot read properties of undefined (reading 'get')"
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:525:34
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid >
const noop = () => {};
<template>
{{on 'click' noop}}
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L525
AssertionError: expected 'message: Parsing error: Cannot read p…' to strictly equal 'message: \'on\' is not defined.'
Expected: "message: 'on' is not defined."
Received: "message: Parsing error: Cannot read properties of undefined (reading 'get')"
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:525:34
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid > import Component from '@glimmer/component';
export default class MyComponent extends Component {
<template>Hello!</template>
}:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L525
AssertionError: expected 'message: Parsing error: Cannot read p…' to strictly equal 'message: Do not create empty backing …'
Expected: "message: Do not create empty backing classes for Glimmer template tag only components."
Received: "message: Parsing error: Cannot read properties of undefined (reading 'get')"
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:525:34
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > invalid >
import { on } from '@ember/modifier';
const noop = () => {};
<template>
<div {{on 'click' noop}} />
</template>
<template>
<div {{on 'click' noop}} />
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L525
AssertionError: expected 'message: Parsing error: Cannot read p…' to strictly equal 'message: Missing semicolon.'
Expected: "message: Missing semicolon."
Received: "message: Parsing error: Cannot read properties of undefined (reading 'get')"
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:525:34
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > valid >
const Foo = <template>hi</template>;
<template>
<Foo />
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L497
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of +0 but got 1
- Expected
+ Received
- 0
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:497:38
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > valid >
import Component from '@glimmer/component';
import { inject as service } from '@ember/service';
export default class MyComponent extends Component {
@service foo;
<template>
{{this.foo}}
<div></div>
foobar
</template>
}
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L497
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of +0 but got 1
- Expected
+ Received
- 0
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:497:38
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > valid >
import Component from '@glimmer/component';
export default class MyComponent extends Component {
foo() {
return this.args.bar + this.args.baz;
}
<template>Hello World!</template>
}
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L497
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of +0 but got 1
- Expected
+ Received
- 0
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:497:38
|
|
tests/lib/rules-preprocessor/gjs-gts-parser-test.js > template-vars > valid >
import { on } from '@ember/modifier';
const noop = () => {};
export default <template>
<div {{on 'click' noop}} />
</template>
:
/tmp/eslint-plugin-ember-test/eslint-plugin-ember/tests/lib/rules-preprocessor/gjs-gts-parser-test.js#L497
AssertionError: expected [ { ruleId: null, fatal: true, …(5) } ] to have a length of +0 but got 1
- Expected
+ Received
- 0
+ 1
❯ tests/lib/rules-preprocessor/gjs-gts-parser-test.js:497:38
|
|
Setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Tests (Node 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Tests (Node 20)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.6, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.3, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.4, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: rc, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: next, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.7, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: next, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.4, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.6, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.3, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.3, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.7, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.5, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.5, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.3, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.6, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.6, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: rc, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.4, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.7, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.5, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: rc, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.5, eslint-ts-deps: canary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.4, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: next, eslint-ts-deps: ^8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: 5.7, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: rc, eslint-ts-deps: ^6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
TS: next, eslint-ts-deps: ^7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
eslint-plugin-ember
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|