This repository was archived by the owner on May 1, 2025. It is now read-only.
Update node #2
Open
Update node #2
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
…l` extension (actions-rs#1) * Add support for rust-toolchain.toml * Add support for reading toml files * bump dist * Add test for toml, fix bug returning wrong type
|
👋 Long time no see! Thanks for the update, and I'll take a look at it next week. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I've been seeing warnings indicating that node v12 which will be forced to v16. There's no reason we can't go ahead and upgrade (or even skip straight to v20). There's also a warning about
set-outputdeprecation... this action is using core though (search forcore.setOutput) so I'm not 100% sure what the upgrade path there is. I can look into it.cc @augustuswm