Upgrade to Go 1.24 and Node 22 #3119
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Cole-Greer
force-pushed
the
runtime-upgrades
branch
from
8c2486b to
f822c55
Compare
Cole-Greer
force-pushed
the
runtime-upgrades
branch
from
f822c55 to
3fd3dbc
Compare
|
VOTE +1 |
|
VOTE +1 pending updates to the docker-compose files as well |
|
https://issues.apache.org/jira/browse/TINKERPOP-3160 was just opened today, we should take a look to see how we can solve the issue of AWS auth breaking with node 22+. #2968 actually may have been a fix for the TINKERPOP-3160 issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Go 1.22 and Node 18 have already past their end of life dates. Upgrading to Go 1.24 and Node 22.
VOTE +1