Update nodejs version specifier
#385
Merged
Conversation
This file contains 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
|
related to rapidsai/integration#509 |
ajschmidt8
added
improvement
|
Converted PR to draft to ensure it doesn't get accidentally merged before e7f2a3c is reverted. |
This was referenced Jul 29, 2022
This reverts commit e7f2a3c.
|
e7f2a3c has passed CI, which means that once rapidsai/integration#509 is merged and its changes propagated, we should be all set here. I will revert e7f2a3c now. |
sevagh
approved these changes
Jul 29, 2022
|
@gpucibot merge |
|
Thanks AJ! 😄 |
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.
The current
nodejsversion specifier is outdated and is causing issues related to #384. This PR updates the specifier to uncap the maximum version and set a new minimum.