[all OSs] Default Nodejs version will be set to 16 on November, 29 #4446
Comments
|
Is there a good place to subscribe to updates like this so we can prepare in advance for it... Or best just to keep an eye on the Issues here in GH? Thanks |
|
All the images are deployed with 16 by default |
1322: Specify node version in CI jobs r=dichotommy a=bidoubiwa # Pull Request ## What does this PR do? Fixes [CI environment that updated to node 16](actions/runner-images#4446) while the documentation is not yet compatible with node 16. ## PR checklist Please check if your PR fulfills the following requirements: - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? Thank you so much for contributing to MeiliSearch! Co-authored-by: Charlotte Vermandel <charlottevermandel@gmail.com>
|
@ejntaylor we subscribed to github releases for this repo so that we are notified in the future |
|
Is there a better way to communicate breaking changes like this? Changes like this has to be communicated on the organization level of the consumers of this service, not the individual github users. We are now, again, having breaking builds due to the lack of proper communication regarding changes in Azure. |
|
@phun-ky Sorry for the inconvenience. I will raise this issue internally and we will try to figure out possible announcement options for ADO |
|
@miketimofeev the issue is a zlib error (isaacs/minizlib#8 (comment)) from npm with the |
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Even though Node v16 is the default actions/runner-images#4446 be explicit about the version needed, because future updates may break CI
Breaking changes
We are going to set Nodejs 16 as the default version across all VM images.
Target date
Image deployment is starting on November 29 and will take 3-4 days.
The motivation for the changes
Node.js 16 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 14 or npm 6 they can be broken.
Virtual environments affected
Mitigation ways
The recommended way is to pin your workflow to the desired nodejs version using:
The text was updated successfully, but these errors were encountered: