Skip to content

feat: upgrade to node 24#17

Open
BrandonT95 wants to merge 1 commit into
mainfrom
feat/VOL-7093
Open

feat: upgrade to node 24#17
BrandonT95 wants to merge 1 commit into
mainfrom
feat/VOL-7093

Conversation

@BrandonT95
Copy link
Copy Markdown
Contributor

@BrandonT95 BrandonT95 commented May 21, 2026

Description

This pull request updates the project to use Node.js 24, including all relevant configuration files, dependencies, and documentation. It also includes minor improvements to documentation and updates some package versions for compatibility.

Node.js version upgrade:

  • Updated the Node.js version from 22 to 24 in .github/workflows/ci.yml, .nvmrc, package.json, and template.yml to standardize the environment across CI, local development, and deployment. [1] [2] [3] [4] [5]
  • Updated the required Node.js version in the README.md to reflect the new standard.

Dependency updates for Node.js 24 compatibility:

  • Upgraded @types/node to ^24.12.4, aws-sam-webpack-plugin to ^0.16.0, and https-proxy-agent to ^7.0.6 in package.json to ensure compatibility with Node.js 24. [1] [2]

Code compatibility:

  • Updated the type of requestAgent in src/services/cognito.ts to HttpsProxyAgent<string> | undefined to align with the latest https-proxy-agent typings.

Documentation and configuration improvements:

  • Clarified instructions in README.md for creating and invoking events, and updated environment variable names for clarity (e.g., COGNITO_CLIENT_ID to COGNITO_CLIENT_ID_1). [1] [2]

These changes ensure the project is up-to-date with the latest Node.js LTS version and compatible dependencies, while also improving clarity in documentation and configuration.

Related issue: VOL-7093

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have performed a self-review of my own code
  • I have added tests that prove my fix is effective or that my feature works

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant