-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update types/node16 to 20 and v3 in readmes #1326
Update types/node16 to 20 and v3 in readmes #1326
Conversation
@bethanyj28, maybe you might be able to take a look at this and at the confirmed #1323? |
@yacaovsnc, @robherley, could you please reach out to someone to have a look at this PR and issue #1323?
|
f308c3d
to
5a51ca9
Compare
examples.md
Outdated
@@ -46,7 +46,7 @@ | |||
Using [NuGet lock files](https://docs.microsoft.com/nuget/consume-packages/package-references-in-project-files#locking-dependencies): | |||
|
|||
```yaml | |||
- uses: actions/cache@v3 | |||
- uses: actions/cache@v4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This repo seems to be lacking maintenance attention. It may be helpful to make some noise on here https://github.com/orgs/community/discussions/121811 |
Co-authored-by: Josh Gross <joshmgross@github.com>
bump. At least run CI? Leaving this action like this seems very counter to the whole github actions push to update to node 20. |
Since #1323 (comment) has already been resolved and was an unrelated issue, I don't think we need these changes. Feel free to reopen if you feel otherwise. |
Untested (not a js dev), but should not need any remarks else than:
Commit 1 may be one step forward to help to fix #1323, best wishes to remove all node16 deps.
But that does not explain why the GitHub annotation still talks that it is cache@v3 and not v4...
yargs also uses a 16.x.x number in package-lock.json, setup-python uses a 17.x.x version, maybe it and others need updating too