[all OSs] Default Nodejs version will be set to 18 on February, 13 #7002

mikhailkoliada · 2023-01-28T16:04:41Z

Breaking changes

We are going to set Nodejs 18 as the default version across all VM images.

Target date

Image deployment is starting on February 13 and will take 3-4 days.

The motivation for the changes

Node.js 18 has moved to Active LTS status and is ready for general use. We would like to provide images with the latest stable updates as default ones.

Possible impact

If your builds depend on the default Nodejs 16 they can be broken.

Platforms affected

Azure DevOps
GitHub Actions

Runner images affected

Mitigation ways

The recommended way is to pin your workflow to the desired nodejs version using:

https://github.com/actions/setup-node action for GH
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/node-js?view=azure-devops for AzDO

aeisenberg · 2023-01-30T04:12:05Z

I think the description of this issue is incorrect. Do you mean to say node 18?

mikhailkoliada · 2023-01-30T09:37:39Z

Right, fixed, thanks!

jaden-zerbe-kr · 2023-02-06T19:28:10Z

Will this enable the creation of GitHub javascript actions using node18? https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-for-javascript-action

mikhailkoliada · 2023-02-12T11:44:16Z

Will this enable the creation of GitHub javascript actions using node18? https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-for-javascript-action

@jaden-zerbe-kr no, it is just a change of default for setup-node and some other tasks

jaden-zerbe-kr · 2023-02-13T13:55:43Z

Will this enable the creation of GitHub javascript actions using node18? https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-for-javascript-action

@jaden-zerbe-kr no, it is just a change of default for setup-node and some other tasks

Is this an appropriate repository to make such a feature request? If not, are you aware of the appropriate repository or an existing request for this to be supported?

glenpogz36 · 2023-02-16T07:06:01Z

Is there any way I could still run these with node16??

If yes, how can I specify my azure pipeline to run node 16

It seems my agent pool is now running version 18 causing my pipeline run build to break

glenpogz36 · 2023-02-16T07:06:55Z

at NormalModule._initBuildHash (D:\a\1\s\node_modules\webpack\lib\NormalModule.js:417:16)
at handleParseError (D:\a\1\s\node_modules\webpack\lib\NormalModule.js:471:10)
at D:\a\1\s\node_modules\webpack\lib\NormalModule.js:503:5
at D:\a\1\s\node_modules\webpack\lib\NormalModule.js:358:12
at D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at iterateNormalLoaders (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:221:10)
at D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:236:3
at runSyncOrAsync (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:130:11)
at iterateNormalLoaders (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:232:2)
at Array.<anonymous> (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (D:\a\1\s\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at D:\a\1\s\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9

D:\a\1\s\node_modules\react-scripts\scripts\build.js:19
throw err;
^

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (D:\a\1\s\node_modules\webpack\lib\util\createHash.js:135:53)
at NormalModule._initBuildHash (D:\a\1\s\node_modules\webpack\lib\NormalModule.js:417:16)
at D:\a\1\s\node_modules\webpack\lib\NormalModule.js:452:10
at D:\a\1\s\node_modules\webpack\lib\NormalModule.js:323:13
at D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:367:11
at D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:233:18
at context.callback (D:\a\1\s\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
at D:\a\1\s\node_modules\react-scripts\node_modules\babel-loader\lib\index.js:59:103 {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.14.0

guitoux1 · 2023-02-16T09:34:29Z

Same issue here, I need to use Node 1, no 18.
My npm task in set inside a .csproj as a BeforeBuild task, and in my devops yml task it's just a VSBuild task, so I don"t have anu control on the NPM version used.

TomasHubelbauer · 2023-02-16T11:07:16Z

@guitoux1 I think you should be able to use https://github.com/actions/setup-node. That is how you can control the global NPM version.

prabhaskumra · 2023-02-16T22:34:29Z

Is there any way I could still run these with node16??

If yes, how can I specify my azure pipeline to run node 16

It seems my agent pool is now running version 18 causing my pipeline run build to break

You can add a task to set a specific version of nodejs. The following way is how I did it, I needed version 16.13.1.

- task: NodeTool@0
  inputs:
    versionSource: 'spec'
    versionSpec: '16.13.1'

vibhuti1 · 2023-02-16T23:33:16Z

Is there any way I could still run these with node16??

If yes, how can I specify my azure pipeline to run node 16

It seems my agent pool is now running version 18 causing my pipeline run build to break

You can add a "Node.js tool installer" task in your job before the "npm install" task and specify the Node version you want to use.
It will download and use the same Node version for the subsequent tasks.

The default node version for the runners was changed to 18, which is not compatible with our current setup. Unfortunately, this change was not properly announced, which is why we did not notice it. There is only a GH issue about it at the moment. actions/runner-images#7002 In order to fix this, we need to explicitly set the node version to 16 for all our workflows that use node/pnpm.

mikhailkoliada · 2023-02-18T17:39:03Z

Deployed

The issues appears to be related to actions/runner-images#7002. Co-authored-by: Ms2ger <Ms2ger@igalia.com>

grzegorzjudas · 2023-03-15T13:48:57Z

@WillBeebe I don't think it does. You're just checking what node version is used in the runner after your custom action completes - doesn't mean the action between is using it.

To test I did the same and had the action print process.version:

grzegorzjudas · 2023-03-15T13:51:16Z

@mikhailkoliada node v18 is now LTS (since 2022-10-25, so almost 5 months now). When can we expect support for using: node18 in custom JavaScript actions?

@thibaudmichaud

* [spec] Add reference types to overview (WebAssembly#1394) * [interpreter] Remove use of physical equality on characters (WebAssembly#1396) * Merge SIMD proposal (WebAssembly#1391) SIMD is [phase 5](WebAssembly/simd#507), merge all the changes back into main spec. * Remove merge conflict marker * [spec] Handle v128 in validation algorithm (WebAssembly#1399) * [spec] Fix instruction table (WebAssembly#1402) * Add tests for functions without end marker. NFC (WebAssembly#1405) Inspired by this downstream test in wabt: WebAssembly/wabt#1775 Fixes: WebAssembly#1404 * Describe correct tail call behavior across modules Whether tail calls across module boundaries would guarantee tail call behavior was previously an open question, but @thibaudmichaud confirmed that they would guarantee tail call behavior in V8 in WebAssembly/tail-call#15 (comment). * [interpreter] Fix a typo in README (WebAssembly#1406) * Add a link to the proposals repo (WebAssembly#1409) Fixes WebAssembly#1407. * [spec] Add note regarding parameter names (WebAssembly#1412) * Comments WIP * Merge upstream (WebAssembly#55) * Typo * [spec] Clarifying note on text format (WebAssembly#1420) Signed-off-by: Adrian Cole <adrian@tetrate.io> Co-authored-by: Andreas Rossberg <rossberg@mpi-sws.org> * Eps * Eps * [test] Fix section size in binary test (WebAssembly#1424) * Update document README to install six * Disallow type recursion (WebAssembly#56) * Fix import order * Add --generate-js-only flag to test runner This will return early right after generating JS from the wast test files. It will not attempt to run the tests, or do the round trip conversion from wasm <-> wast. This is convenient for proposals to add tests without having to update the reference interpreter with implementation, and generate those tests to JS to run in other Wasm engines. Fixes WebAssembly#1430. * Remove use of let from func.bind test * Add call3 * [spec] Fix missing mention of vectype (WebAssembly#1436) Fixed WebAssembly#1435. * [spec] Fix single-table limitation in module instantiation (WebAssembly#1434) * [spec] Fix missing immediate on table.set (WebAssembly#1441) * [docs] Update syntax in examples (WebAssembly#1442) * Clarification in proposals README * [interpreter] Tweak start section AST to match spec * [spec] Bump release to 2 (WebAssembly#1443) At yesterday's WG meeting, we decided to make a new release, now switching to the Evergreen model. For administrative and technical reasons having to do with W3C procedure, we decided to bump the release number to 2. From now on, the standard will iterate at version 2 from the W3C's official perspective. We use minor release numbers internally to distinguish different iterations. (@ericprud, I hope I understood correctly that the Bikeshed "level" also needed to be bumped to 2.) * Remove test cases with let * Sync wpt test (WebAssembly#1449) * [spec] Fix typo (WebAssembly#1448) * [proposals] Add missing start to example (WebAssembly#1454) * [spec] "version 2.0" -> "release 2.0" (WebAssembly#1452) * [spec] Fix typo (WebAssembly#1458) * [test] Add assert_trap for unreached valid case (WebAssembly#1460) * [interpreter] Name the type Utf8.unicode * [spec] Fix binary format of data/elem tags to allow LEB (WebAssembly#1461) * [spec] Fix typos in numeric operations (WebAssembly#1467) * [spec] Fix syntax error in element segments validation rule (WebAssembly#1465) * [spec] Fix typo in global instance syntax (WebAssembly#1466) * [spec] Fix typos in module instantiation (WebAssembly#1468) * [interpreter] Turn into a Dune package (WebAssembly#1459) * [spec] Fix typos in instruction validation rules (WebAssembly#1462) * [bib] Update latex .bib file for webassembly 2.0 (WebAssembly#1463) * [spec] Add missing default for vector types (WebAssembly#1464) * [spec] Fix typos in binary and text formats (WebAssembly#1469) * [spec] Fix various typos (WebAssembly#1470) * TypeError for Global constructor with v128 At the moment the spec requires a `LinkError` to be thrown when the `WebAssembly.Global` constructor is called for type `v128`. This was introduced in WebAssembly/simd#360, but according to the PR description, actually a `TypeError` should be thrown. The PR refers to https://github.com/WebAssembly/simd/blob/master/proposals/simd/SIMD.md#javascript-api-and-simd-values, and there a `TypeError` is required. * [spec] Fix LEB opcodes in instruction index (WebAssembly#1475) * [spec] Fix v128.loadX_splat in instruction index (WebAssembly#1477) * [interpreter] Dune test suite (WebAssembly#1478) * [interpreter] Fix warning flags for OCaml 4.13 (WebAssembly#1481) * [interpreter] Simplify lexer and avoid table overflow on some architectures (WebAssembly#1482) * [spec] Editorial nit (WebAssembly#1484) * [interpreter] Produce error messages in encoder (WebAssembly#1488) * [spec] Add missing close paren on table abbreviation (WebAssembly#1486) Also remove an unnecessary space in the previous table abbreviation. * [spec] Remove outdated note (WebAssembly#1491) * Eps * [interpreter] Factor data and element segments into abstract types (WebAssembly#1492) * [spec] Update note on module initialization trapping (WebAssembly#1493) * Fix type equality * Fix typo * [spec] Add note about control stack invariant to algorithm (WebAssembly#1498) * [spec] Tweak tokenisation for text format (WebAssembly#1499) * [test] Use still-illegal opcode (func-refs) (WebAssembly#1501) * Fix minor typos and consistency issues in the validation algorithm. (WebAssembly#61) * Add definition of defaultable types (WebAssembly#62) No rules for locals yet, since those are still being discussed. * Remove func.bind (WebAssembly#64) * Implement 1a (WebAssembly#63) * Subtyping on vector types & heap bottom check (WebAssembly#66) * [interpreter] Bring AST closer to spec * [spec] Fix typo (WebAssembly#1508) * WIP * Remove polymorphic variants * Minor syntactic consistency fix (WebAssembly#68) Change pseudo equality operator from `==` to `=`. * Bump version * [spec] Fix table.copy validation typo (WebAssembly#1511) * More fixes * Fix Latex * Adjust intro * Spec local initialization (WebAssembly#67) * Add table initialiser (WebAssembly#65) * [spec] Remove outdated note (WebAssembly#1491) * [interpreter] Factor data and element segments into abstract types (WebAssembly#1492) * [spec] Update note on module initialization trapping (WebAssembly#1493) * [spec] Add note about control stack invariant to algorithm (WebAssembly#1498) * [spec] Tweak tokenisation for text format (WebAssembly#1499) * [test] Use still-illegal opcode (func-refs) (WebAssembly#1501) * [spec] Fix typo (WebAssembly#1508) * [spec] Fix table.copy validation typo (WebAssembly#1511) * Merge fallout * Latex fixes * [spec] Minor copy edit (WebAssembly#1512) * Spec changelog * [spec] Trivial editorial fix * Update embedding * Oops * Argh * Rename Sem to Dyn * Readd match.mli * [interpreter] Build wast.js with Js_of_ocaml (WebAssembly#1507) * [interpreter] Add flag for controlling call budget * Spec zero byte * Fix table/elem expansion (WebAssembly#71) * Fix merge artefact * Restrict init from stack-polymorphism (WebAssembly#75) * [spec] Simplify exec rule for if (WebAssembly#1517) * [spec] Formatting tweak (WebAssembly#1519) * [spec] Fix typing rule in appendix (WebAssembly#1516) * [spec] Fix “invertible” typo (WebAssembly#1520) * [spec] Correct use of opdtype and stacktype (WebAssembly#1524) * [spec] Add note to instruction index (WebAssembly#1528) * Add type annotation to call_ref (WebAssembly#76) * [spec] Tweak wording to avoid first person * Eps * Eps2 * Eps3 * Remove unneeded assumption type * [spec/test] Fix scoping of non-imported globals (WebAssembly#1525) * Fix test * A couple of tests * Performance improvement * Typo * Another typo * [spec] Fix language config * Fix null subtyping being wrong way around (WebAssembly#79) * [spec] Fix naming typo (WebAssembly#1532) * Defunctorise types again * [spec] Add citation for WasmCert (WebAssembly#1533) * [test] Fix async_index.js * [test] Enable the i64 tests in imports.wast. Fixes WebAssembly#1514. * Minor tweak * [js-api][web-api] Editorial: Fix some minor issues. Fixes WebAssembly#1064. * Update README.md (WebAssembly#1540) Improve wording. * [spec] Fix typo in element execution (WebAssembly#1544) * [spec] Remove obsolete note (WebAssembly#1545) * cccccc[klghketetivvtnnhvntikigrnueuhdkkukljgjuest/meta/generate_*.js: sync upstream JS with tests (WebAssembly#1546) * [spec] Editorial tweak * [test] test segment/table mismatch and externref segment (WebAssembly#1547) * [interpreter] Remove duplicate token declarations (WebAssembly#1548) * Update Soundness appendix (WebAssembly#72) * [spec] Formatting eps * Remove oboslete note in README (WebAssembly#82) * Add `print_i64` to generated spec tests WebAssembly@82a613d added `print_i64` to the standalone test files, but not to the ones generated by the spec interpreter. * [test] Tweak binary-leb128 and simd_lane (WebAssembly#1555) * [spec] Allow explicit keyword definitions (WebAssembly#1553) Rather than describing keyword tokens as always being defined implicitly by terminal symbols in syntactic productions, describe them as being defined implicitly or explicitly. This accounts for the explicit definitions of `offset` and `align` phrases, which are lexically keywords, later in the chapter. Fixes WebAssembly#1552. * [js-api] editorial: adjust link for v128 type * Factor local init tests to local_init.wast; add more (WebAssembly#84) * Update JS API for no-frills * [spec] Add missing case for declarative elem segments Fixes WebAssembly#1562. * [spec] Hotfix last accidental commit * [spec] Fix hyperref (WebAssembly#1563) * [spec] Bump sphinx version to fix Python problem * [spec] Fix minor errors and inconsistencies (WebAssembly#1564) * Spacing * Fix a couple more superfluous brackets * [spec] Eps * [interpreter] Refactor parser to handle select & call_indirect correctly (WebAssembly#1567) * [spec] Remove dead piece of grammar * [test] elem.wast: force to use exprs in a element (WebAssembly#1561) * Fix typos in SIMD exec/instructions * Update interpreter README (WebAssembly#1571) It previously stated that the formal spec did not exist, but the spec has existed for years now. * [spec] Remove an obsolete exec step (WebAssembly#1580) * [test] Optional tableidx for table.{get,set,size,grow,fill} (WebAssembly#1582) * [spec] Fix abstract grammar for const immediate (WebAssembly#1577) * [spec] Fix context composition in text format (WebAssembly#1578) * [spec] Fix label shadowing (WebAssembly#1579) * Try bumping OCaml * Try bumping checkout * Adjust for multi-return * Tweak reduction rules * Spec return_call_ref * Fix * Text format * [spec] Fix typos in instruction index (WebAssembly#1584) * [spec] Fix typo (WebAssembly#1587) * [spec] Remove inconsistent newline (WebAssembly#1589) * [interpreter] Remove legacy bigarray linking (WebAssembly#1593) * [spec] Show scrolls for overflow math blocks (WebAssembly#1594) * [interpreter] Run JS tests via node.js (WebAssembly#1595) * [spec] Remove stray `x` indices (WebAssembly#1598) * [spec] Style tweak for cross-refs * [spec] Style eps (WebAssembly#1601) * Separate subsumption from instr sequencing * State principal types * Add statements about glbs, lubs, and disjoint hierarchies * Add missing bot * [spec] Clarify that atoms can be symbolic (WebAssembly#1602) * [test] Import v128 global (WebAssembly#1597) * Update Overview.md * [js-api] Expose everywhere * [js-api] Try to clarify NaN/infinity handling. (WebAssembly#1535) * [web-api] Correct MIME type check. (WebAssembly#1537) Fixes WebAssembly#1138. * [ci] Pin nodejs version to avoid fetching failures (WebAssembly#1603) The issues appears to be related to actions/runner-images#7002. Co-authored-by: Ms2ger <Ms2ger@igalia.com> * [spec] Add missing value to table.grow reduction rule (WebAssembly#1607) * [test] Move SIMD linking test to simd dir (WebAssembly#1610) * Editorial: Clarify the name of the instantiate algorithm. * Add notes to discourage using synchronous APIs. * [jsapi] Normative: Always queue a task during asynchronous instantiation JSC will have to do asynchronous compilation work during some instantiations. To be consistent, this PR always queues a task to complete instantiation, except through the synchronous Instance(module) API, to ensure consistency across platforms. This patch also cleans up the specification in various surrounding ways: - Include notes about APIs whose use is discouraged/may be limited Closes WebAssembly#741 See also webpack/webpack#6433 * [test] Exception -> Tag in wasm-module-builder.js The section name has changed to the tag section a few years ago. This adds the corresponding changes added in WebAssembly/exception-handling#252 and WebAssembly/exception-handling#256. * [spec] Fix reduction rule for label (WebAssembly#1612) Fix WebAssembly#1605. * [spec] Clarifying note about canonical NaNs (WebAssembly#1614) * [spec] Tweak crossref * [test] Fix invalid section ID tests (WebAssembly#1615) * [tests] Disable node run for now * [spec] Don't check in generated index, to avoid spurious merge conflicts * [spec] Rename script * [ci] deactivate node run for now * Fix uses of \to; compositionality * Fix typo in text expansion * Follow-up fix * Fix compilation errors after merge. This commit fixes the errors introduced by the merge of function-references/main into this tree. --------- Signed-off-by: Adrian Cole <adrian@tetrate.io> Co-authored-by: Andreas Rossberg <rossberg@dfinity.org> Co-authored-by: Hans Höglund <hanshoglund@users.noreply.github.com> Co-authored-by: Ng Zhi An <zhin@chromium.org> Co-authored-by: Ng Zhi An <zhin@google.com> Co-authored-by: Sam Clegg <sbc@chromium.org> Co-authored-by: Thomas Lively <7121787+tlively@users.noreply.github.com> Co-authored-by: Gabor Greif <ggreif@gmail.com> Co-authored-by: Andreas Rossberg <rossberg@mpi-sws.org> Co-authored-by: Crypt Keeper <64215+codefromthecrypt@users.noreply.github.com> Co-authored-by: Andreas Rossberg <rossberg@chromium.org> Co-authored-by: Ng Zhi An <ngzhian@gmail.com> Co-authored-by: Ben L. Titzer <ben.titzer@gmail.com> Co-authored-by: Keith Winstein <keithw@cs.stanford.edu> Co-authored-by: gahaas <ahaas@google.com> Co-authored-by: r00ster <r00ster91@protonmail.com> Co-authored-by: Timothy McCallum <tpmccallum@users.noreply.github.com> Co-authored-by: Julien Cretin <github@ia0.eu> Co-authored-by: Julien Cretin <cretin@google.com> Co-authored-by: Ole Krüger <ole@vprsm.de> Co-authored-by: Jämes Ménétrey <james@menetrey.me> Co-authored-by: Ivan Panchenko <39594356+ivan-pan@users.noreply.github.com> Co-authored-by: Ethan Jones <ictrobot@outlook.com> Co-authored-by: Ole Krüger <ole.kruger@trili.tech> Co-authored-by: aathan <aathan_github@memeplex.com> Co-authored-by: Alberto Fiori <9143617+fifofefe@users.noreply.github.com> Co-authored-by: mnordine <marknordine@gmail.com> Co-authored-by: cosine <CosineP@users.noreply.github.com> Co-authored-by: ariez-xyz <41232910+ariez-xyz@users.noreply.github.com> Co-authored-by: Surma <surma@surma.dev> Co-authored-by: Asumu Takikawa <asumu@igalia.com> Co-authored-by: Ian Henderson <ian@ianhenderson.org> Co-authored-by: Tom Stuart <hi@tomstu.art> Co-authored-by: James Browning <thejamesernator@gmail.com> Co-authored-by: whirlicote <78504913+whirlicote@users.noreply.github.com> Co-authored-by: Ms2ger <Ms2ger@igalia.com> Co-authored-by: Adam Lancaster <Adzz@users.noreply.github.com> Co-authored-by: Ömer Sinan Ağacan <omeragacan@gmail.com> Co-authored-by: B Szilvasy <beatrice.szilvasy@gmail.com> Co-authored-by: Thomas Lively <tlively123@gmail.com> Co-authored-by: Michael Ficarra <github@michael.ficarra.me> Co-authored-by: YAMAMOTO Takashi <yamamoto@midokura.com> Co-authored-by: Thomas Lively <tlively@google.com> Co-authored-by: candymate <31069474+candymate@users.noreply.github.com> Co-authored-by: Bongjun Jang <bongjun.jang@kaist.ac.kr> Co-authored-by: ShinWonho <50018375+ShinWonho@users.noreply.github.com> Co-authored-by: 서동휘 <hwidongsuh@gmail.com> Co-authored-by: Jim Blandy <jimb@red-bean.com> Co-authored-by: Heejin Ahn <aheejin@gmail.com> Co-authored-by: Daniel Ehrenberg <littledan@chromium.org>

ihnorton · 2023-03-29T12:45:19Z

This change means that GHA (and AZP) container jobs can no longer use CentOS 7 or Ubuntu 20 images with default settings.

Shell task in a CentOS 7 container:

/__a/externals/node16/bin/node: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /__a/externals/node16/bin/node)

kekel87 · 2023-06-08T13:18:51Z

Hello, I can't figure out if this is supported now or not?

vpolikarpov-akvelon · 2023-06-09T15:55:01Z

Hey @kekel87. Could you elaborate your question?

actions/runner-images#7002

## Description - Pins GitHub actions that now default to node 18 to node 16 - sets node engine to 16 in `package.json` ## Motivation and Context    All of our jest tests the imported files using `data-forge` were failing to run. Something must break when running on node 18 (the new default) instead of node 16, so for now this PR pins our yaml files to node 16 actions/runner-images#7002 ## Has this been tested? How?    Tests are passing again ## Types of changes  - Chore (developer productivity fix that doesn't affect the user)

The issues appears to be related to actions/runner-images#7002. Co-authored-by: Ms2ger <Ms2ger@igalia.com>

mikhailkoliada added Area: JavaScript and Node.js OS: macOS OS: Ubuntu OS: Windows Announcement labels Jan 28, 2023

mikhailkoliada pinned this issue Jan 28, 2023

mikhailkoliada changed the title ~~[all OSs] Default Nodejs version will be set to 16 on February, 13~~ [all OSs] Default Nodejs version will be set to 18 on February, 13 Jan 30, 2023

Christoba mentioned this issue Feb 2, 2023

ArchiveFiles@2 fails due to Node 16 missing #7037

Closed

10 tasks

sethvargo mentioned this issue Feb 7, 2023

NodeJS 18x google-github-actions/setup-gcloud#614

Closed

mikhailkoliada self-assigned this Feb 12, 2023

This was referenced Feb 12, 2023

[Windows] set node 18 as default #7092

Merged

[macOS] set node 18 as default #7093

Merged

[Ubuntu] set node 18 as default #7094

Merged

mikhailkoliada added the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Feb 13, 2023

michelkaporin mentioned this issue Feb 17, 2023

fix: smoke test matrix snyk/cli#4426

Merged

1 task

ardelato mentioned this issue Feb 18, 2023

Hot Fix: Make Runners Explicitly use Node Version 16 iFixit/react-commerce#1381

Merged

billy1624 mentioned this issue Feb 18, 2023

[CI] downgrade to Node v16 SeaQL/seaql.github.io#92

Merged

1 task

DeeDeeG mentioned this issue Feb 24, 2023

Add Setup Node to Package Tests pulsar-edit/pulsar#399

Merged

This was referenced Feb 24, 2023

Test builds are failing (except on macOS) julia-actions/setup-julia#135

Closed

Pin node version to v16. Fix #135 julia-actions/setup-julia#145

Merged

tibdex mentioned this issue Feb 27, 2023

Upgrade to Node.js 18 tibdex/github-app-token#68

Closed

shubhbapna mentioned this issue Feb 28, 2023

prepare for node 18 kiegroup/github-action-build-chain#405

Open

6 tasks

rossberg pushed a commit to WebAssembly/multi-memory that referenced this issue Mar 1, 2023

[ci] Pin nodejs version to avoid fetching failures (#1603)

a7a2da4

The issues appears to be related to actions/runner-images#7002. Co-authored-by: Ms2ger <Ms2ger@igalia.com>

FraBle mentioned this issue Mar 9, 2023

Make scope optional MondoPower/codeartifact-auth#6

Merged

EelcoLos mentioned this issue Mar 15, 2023

feat: updates regarding dependabot issues. node 18 workflow & engine update amannn/action-semantic-pull-request#229

Merged

dkwon17 mentioned this issue Mar 27, 2023

[BUG] Failing Check Distribution Check redhat-actions/try-in-web-ide#28

Closed

humphd mentioned this issue Apr 3, 2023

Update dependencies and use node18 navied/secure-webhook#3

Open

yeikel mentioned this issue Apr 7, 2023

Add .devcontainer dependabot/fetch-metadata#334

Closed

Magellol mentioned this issue May 8, 2023

Fix CI job unsplash/unsplash-js#203

Merged

alessio-perugini mentioned this issue May 19, 2023

chore: update @types/node from ^12.0.4 to ^18.11.17 arduino/setup-protoc#62

Closed

0x2b3bfa0 mentioned this issue Jun 3, 2023

Pin Node.js version on GitHub Actions test job iterative/cml#1382

Merged

iowillhoit mentioned this issue Jun 9, 2023

feat: validate new issues GHA forcedotcom/cli#2190

Merged

eitu5ami added a commit to 0xProject/setup-govulncheck that referenced this issue Jul 5, 2023

Switch to NodeJS 18

2b33a5f

actions/runner-images#7002

eitu5ami mentioned this issue Jul 5, 2023

Switch to NodeJS 18 0xProject/setup-govulncheck#49

Merged

eitu5ami added a commit to 0xProject/setup-govulncheck that referenced this issue Jul 5, 2023

Switch to NodeJS 18

91a6c6b

actions/runner-images#7002

bendrucker mentioned this issue Aug 1, 2023

build(deps): Bump @octokit/rest from 19.0.13 to 20.0.1 terraform-linters/setup-tflint#184

Merged

fgmccabe pushed a commit to WebAssembly/js-promise-integration that referenced this issue Mar 5, 2024

[ci] Pin nodejs version to avoid fetching failures (#1603)

854c8d4

The issues appears to be related to actions/runner-images#7002. Co-authored-by: Ms2ger <Ms2ger@igalia.com>

e-maad mentioned this issue Sep 26, 2024

chore: update node version (20) for test_build_deploy wireapp/wire-account#4997

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[all OSs] Default Nodejs version will be set to 18 on February, 13 #7002

[all OSs] Default Nodejs version will be set to 18 on February, 13 #7002

mikhailkoliada commented Jan 28, 2023

aeisenberg commented Jan 30, 2023 •

edited

Loading

mikhailkoliada commented Jan 30, 2023

jaden-zerbe-kr commented Feb 6, 2023

mikhailkoliada commented Feb 12, 2023

jaden-zerbe-kr commented Feb 13, 2023

glenpogz36 commented Feb 16, 2023

glenpogz36 commented Feb 16, 2023

guitoux1 commented Feb 16, 2023

TomasHubelbauer commented Feb 16, 2023

prabhaskumra commented Feb 16, 2023 •

edited

Loading

vibhuti1 commented Feb 16, 2023 •

edited

Loading

mikhailkoliada commented Feb 18, 2023

grzegorzjudas commented Mar 15, 2023

grzegorzjudas commented Mar 15, 2023 •

edited

Loading

ihnorton commented Mar 29, 2023 •

edited

Loading

kekel87 commented Jun 8, 2023

vpolikarpov-akvelon commented Jun 9, 2023

[all OSs] Default Nodejs version will be set to 18 on February, 13 #7002

[all OSs] Default Nodejs version will be set to 18 on February, 13 #7002

Comments

mikhailkoliada commented Jan 28, 2023

Breaking changes

Target date

The motivation for the changes

Possible impact

Platforms affected

Runner images affected

Mitigation ways

aeisenberg commented Jan 30, 2023 • edited Loading

mikhailkoliada commented Jan 30, 2023

jaden-zerbe-kr commented Feb 6, 2023

mikhailkoliada commented Feb 12, 2023

jaden-zerbe-kr commented Feb 13, 2023

glenpogz36 commented Feb 16, 2023

glenpogz36 commented Feb 16, 2023

guitoux1 commented Feb 16, 2023

TomasHubelbauer commented Feb 16, 2023

prabhaskumra commented Feb 16, 2023 • edited Loading

vibhuti1 commented Feb 16, 2023 • edited Loading

mikhailkoliada commented Feb 18, 2023

grzegorzjudas commented Mar 15, 2023

grzegorzjudas commented Mar 15, 2023 • edited Loading

ihnorton commented Mar 29, 2023 • edited Loading

kekel87 commented Jun 8, 2023

vpolikarpov-akvelon commented Jun 9, 2023

aeisenberg commented Jan 30, 2023 •

edited

Loading

prabhaskumra commented Feb 16, 2023 •

edited

Loading

vibhuti1 commented Feb 16, 2023 •

edited

Loading

grzegorzjudas commented Mar 15, 2023 •

edited

Loading

ihnorton commented Mar 29, 2023 •

edited

Loading