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.

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

upgrade bot to node 20 #151

Closed
Ethazeriel opened this issue Jan 11, 2024 · 1 comment · Fixed by #152
Closed

upgrade bot to node 20 #151

Ethazeriel opened this issue Jan 11, 2024 · 1 comment · Fixed by #152
Labels
maintenance maintenance of existing infrastructure

Comments

@Ethazeriel
Copy link
Owner

node 18 has reached the maintenance stage of its lifecycle, so sometime this year we should move to node 20 (or 22 depending how much we procrastinate)

this should be relatively easy on the server side, probably a bit messier for the client as we'll likely have to move off CRA at the same time.

@Ethazeriel Ethazeriel added the maintenance maintenance of existing infrastructure label Jan 11, 2024
@Ethazeriel
Copy link
Owner Author

forgot that the opus package was why we were using an older node version on the server.

in any case, needs testing but implemented in #152

@Ethazeriel Ethazeriel linked a pull request Jan 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance maintenance of existing infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant