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

Update types/node16 to 20 and v3 in readmes #1326

Conversation

bernhardkaindl
Copy link

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

@bernhardkaindl
Copy link
Author

@bethanyj28, maybe you might be able to take a look at this and at the confirmed #1323?

@bernhardkaindl
Copy link
Author

bernhardkaindl commented Mar 22, 2024

@yacaovsnc, @robherley, could you please reach out to someone to have a look at this PR and issue #1323?

@bethanyj28, maybe you might be able to take a look at this and at the confirmed #1323?

@actions-cache

@bernhardkaindl bernhardkaindl force-pushed the update-types/node16-to-20-and-v3-in-readmes branch from f308c3d to 5a51ca9 Compare March 22, 2024 19:16
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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@IanButterworth
Copy link

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

examples.md Outdated Show resolved Hide resolved
@IanButterworth
Copy link

bump. At least run CI?

Leaving this action like this seems very counter to the whole github actions push to update to node 20.

@joshmgross
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Updated to actions/cache@v4, but that does not stop the Node16 warning on v3
8 participants