Skip to content

upgrade node to v24 from v20#23442

Merged
rishabh-gupta-hashicorp merged 2 commits intomainfrom
rishabh-gupta/ui/upgrade-nodejs-to-v22
Apr 20, 2026
Merged

upgrade node to v24 from v20#23442
rishabh-gupta-hashicorp merged 2 commits intomainfrom
rishabh-gupta/ui/upgrade-nodejs-to-v22

Conversation

@rishabh-gupta-hashicorp
Copy link
Copy Markdown
Contributor

Description

Upgrade NodeJS to v22 from v20

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@rishabh-gupta-hashicorp rishabh-gupta-hashicorp requested review from a team as code owners April 8, 2026 10:28
@github-actions github-actions Bot added theme/ui Anything related to the UI type/ci Relating to continuous integration (CI) tooling for testing or releases theme/contributing Additions and enhancements to community contributing materials labels Apr 8, 2026
@rishabh-gupta-hashicorp rishabh-gupta-hashicorp added pr/no-changelog PR does not need a corresponding .changelog entry backport/all Apply backports for all active releases per .release/versions.hcl and removed theme/ui Anything related to the UI type/ci Relating to continuous integration (CI) tooling for testing or releases theme/contributing Additions and enhancements to community contributing materials labels Apr 8, 2026
@rishabh-gupta-hashicorp
Copy link
Copy Markdown
Contributor Author

Closes Issue #23413

@rishabh-gupta-hashicorp rishabh-gupta-hashicorp changed the title upgrade node to v22 from v20 upgrade node to v24 from v20 Apr 13, 2026
Copy link
Copy Markdown
Contributor

@suresh-hashicorp suresh-hashicorp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rishabh-gupta-hashicorp rishabh-gupta-hashicorp merged commit ae3a313 into main Apr 20, 2026
109 of 110 checks passed
@hc-github-team-consul-core hc-github-team-consul-core added backport/1.22 Changes are backported to 1.22 backport/ent/1.18 Changes are backported to 1.18 ent backport/ent/1.21 changes are backported to 1.21 ent labels Apr 20, 2026
@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

📣 Hi @rishabh-gupta-hashicorp! a backport is missing for this PR [23442] for versions [1.18,1.21] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>

2 similar comments
@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

📣 Hi @rishabh-gupta-hashicorp! a backport is missing for this PR [23442] for versions [1.18,1.21] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

📣 Hi @rishabh-gupta-hashicorp! a backport is missing for this PR [23442] for versions [1.18,1.21] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/all Apply backports for all active releases per .release/versions.hcl backport/ent/1.18 Changes are backported to 1.18 ent backport/ent/1.21 changes are backported to 1.21 ent backport/1.22 Changes are backported to 1.22 backport/2.0 Changes are backported to 2.0 pr/no-changelog PR does not need a corresponding .changelog entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants