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

feat: Bump Node.js to version 22 #1794

Closed
rmunn opened this issue Apr 30, 2024 · 0 comments · Fixed by #1797
Closed

feat: Bump Node.js to version 22 #1794

rmunn opened this issue Apr 30, 2024 · 0 comments · Fixed by #1797
Assignees
@rmunn

Comments

@rmunn
Copy link
Collaborator

rmunn commented Apr 30, 2024

Is your feature request related to a problem? Please describe.
Our app Dockerfile uses Node 16, and Node 22 just came out last week. As a first step, we'll bump the version of Node to 18 in #1792. Then we'll bump it to 20 in #1793. And then we'll bump it to 22.

Describe the solution you'd like
Hopefully everything still runs correctly with Node 22.

Describe alternatives you've considered
Staying on Node 20 if 22 would require major rewrites.
@rmunn rmunn mentioned this issue Apr 30, 2024
Merged
6 tasks
@github-project-automation github-project-automation bot moved this from To Do to Awaiting Testing (QA) in Language Forge Classic Apr 30, 2024
This was referenced Apr 30, 2024
Closed
Closed
@rmunn rmunn self-assigned this May 6, 2024
@megahirt megahirt moved this from Awaiting Testing (QA) to Awaiting Deployment in Language Forge Classic Jun 26, 2024
@megahirt megahirt moved this from Awaiting Deployment to Done in Language Forge Classic Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmunn rmunn

Labels
None yet
Projects
Language Forge Classic
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bump node.js version to 22 sillsdev/web-languageforge
1 participant
@rmunn