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

changelog for updating Node #5818

Merged
merged 2 commits into from
Mar 10, 2023
Merged

changelog for updating Node #5818

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d02a487
add changelog
AmitPhulera Mar 9, 2023
f304d02
make
AmitPhulera Mar 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions changelog/0070-update-node-to-v16.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
title: update-node-to-v16
key: update-node-to-v16
date: 2023-03-09
optional_per_env: no
# (optional) Min version of HQ that MUST be deployed before this change can be rolled out (commit hash)
min_commcare_version:
# (optional) Max version of HQ that can be deployed before this change MUST be rolled out (commit hash)
max_commcare_version:
context: |
Node.js 14.x LTS is reaching its end of life 30th April 2023, so node and npm must be upgraded on all machines.
details: |
Because the current LTS version we are using of Node.js (14.x) is reaching its end of life on the 30th of April,
we are upgrading Node.js to the next LTS version 16.19.1. As npm is tightly-coupled with node, we are also upgrading npm to 8.19.3
update_steps: |
To upgrade node.js and npm on your machines please run:
```bash
cchq <env> deploy-stack --tags=npm
```
25 changes: 25 additions & 0 deletions hosting_docs/source/changelog/0070-update-node-to-v16.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
<!--THIS FILE IS AUTOGENERATED: DO NOT EDIT-->
<!--See https://github.com/dimagi/commcare-cloud/blob/master/changelog/README.md for instructions-->
# 70. update-node-to-v16

**Date:** 2023-03-09

**Optional per env:** _required on all environments_


## CommCare Version Dependency
This change is not known to be dependent on any particular version of CommCare.


## Change Context
Node.js 14.x LTS is reaching its end of life 30th April 2023, so node and npm must be upgraded on all machines.

## Details
Because the current LTS version we are using of Node.js (14.x) is reaching its end of life on the 30th of April,
we are upgrading Node.js to the next LTS version 16.19.1. As npm is tightly-coupled with node, we are also upgrading npm to 8.19.3

## Steps to update
To upgrade node.js and npm on your machines please run:
```bash
cchq <env> deploy-stack --tags=npm
```
5 changes: 5 additions & 0 deletions hosting_docs/source/changelog/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,11 @@ need to be applied on your environment to keep it up to date.

### Changelog

#### **2023-03-09** [update-node-to-v16](0070-update-node-to-v16.md)
Node.js 14.x LTS is reaching its end of life 30th April 2023, so node and npm must be upgraded on all machines.


---
#### **2023-01-10** [Configure Java 17 for Formplayer](0069-configure-java-17-for-formplayer.md)
In preparation for the release of Formplayer Java 17 version, we have shipped a few infrastructure changes through Commcare Cloud.
At this point, the ask to those maintaining CommCare instances is to follow the steps below to configure Java 17 for Formplayer.
Expand Down