Conversation
|
Do we need a section to indicate whats new in v3? |
|
Basically, what do users on v2 need to know? |
|
I'd be useful to mention this node update is because of, quoting #689
I'm not sure why this should be a major release, it feels like a lot of churn for every workflow out there, most of them likely running on GH-hosted or recent-enough runners, and for which using a new 2.x release would have been better. Does it mean This feels wrong, people using old runners should pin to a specific release or sha, people using reasonably recent runners should be able to get updates/bug fixes without needing to update all workflows with a new |
|
|
||
| Refer [here](https://github.com/actions/checkout/blob/v1/README.md) for previous versions. | ||
| - Updated to the node16 runtime by default | ||
| - This requires a minimum [Actions Runner](https://github.com/actions/runner/releases/tag/v2.285.0) version of v2.285.0 to run, which is by default available in GHES 3.4 or later. |
There was a problem hiding this comment.
I think it would be worth explicitly mentioning here (and, more importantly, in https://github.com/actions/checkout/releases/tag/v3.0.0) that if you are using github.com (SaaS) you can safely accept the update and ignore the rest of the text.
No description provided.