Nodejs 12 deprecated, upgrade to Nodejs 16. about action-baseline

[derekmurawsky]

Maybe I'm missing something, @kingthorin but those changes were made 6 months ago, but the last release was 0.7.0, which was released on May 23, 2022, which is 9 months ago. Perhaps the new release wasn't cut, so there isn't a newer action available for us to reference?

[thc202]

In the readme it's an example usage.

[kingthorin]

Please contact GitHub, they're displaying that annotation on basically every action/workflow run. It has nothing to do with this action. I see it all over the place all the time.

Duplicate of #83

[thc202]

Actions can be used without a tag or release, you can use the commit or the branch (commit is safer).

[derekmurawsky]

Thanks @thc202 , I'm aware of that capability, however I was following the docs which specify using a release ID, and referenced the current release. I assumed that was what we were supposed to do, and I think that's what most folks reading the docs would assume as well.
I'll switch to using the commit ID for now, but suggest updating the docks, or cutting actual releases.

[kingthorin]

That's fair, thanks for following up.

[thc202]

Which docs?

[kingthorin]

I'm guessing just the repo README

[kingthorin]

Agreed 😀

[houserx-jmcc]

I'm not sure I follow why a new release is being avoided. When browsing Actions in the Marketplace, Github makes it pretty clear that using Releases is an ideal way to target versions - the big green button "Use latest version" defaults to your latest release, which will very soon be pointed towards a broken version.

A lack of current releases also makes it harder to use something like dependabot to stay on top of new action releases.