[BUG] Latest tag does not point to the latest release

[wheeheee]

Describe the bug
As described in the title, the latest tag does not point to the latest release. Discovered when using setup-julia@latest produced the "Node.js 20 actions are deprecated" warning in CI.

To Reproduce
Open up and compare:
https://github.com/julia-actions/setup-julia/tree/v3.0.2
https://github.com/julia-actions/setup-julia/tree/v3
https://github.com/julia-actions/setup-julia/tree/latest

Expected behavior
At this point in time, they should be identical. Their last commits should be the same. It isn't, the latest tag's last commit was 2 years ago. v3 is ok, same as v3.0.2.

Additional context
Not sure if the option to use setup-julia@latest is deprecated, but if not, this is kinda weird.

[DilumAluthge]

Welcome, and thanks for opening this issue!

We actually have deprecated the latest tag on this repo. I announced it on Discourse (https://discourse.julialang.org/t/deprecating-the-latest-and-vx-y-tags-of-the-julia-actions-setup-julia-github-action/136936?u=dilumaluthge), but perhaps we should document it in the README as well.

[wheeheee]

That would be nice. But wouldn't it be better to just delete the latest tag? That would error rather quickly if anyone tried to use it.