[support] Create new tagged release

[mxr576]

I've checked whether the fix from #233 has been included in a tagged release, but it appears it hasn't. The 2.2.0 release is about 1.5 years old, and there are pending changes in the dev branch. Could you please create a new tagged release with those changes? Are there any blockers preventing this from being done? Thanks!

2.2.0...v2

[ruudk]

I'm also waiting for a tagged release that includes #252.

We cannot use @v2 because we always pin to versions, not to branches.

@ramsey Could you please tag a release? Or maybe promote someone to handle it for you?

[ramsey]

2.3.0 is tagged

[mxr576]

Thank you! 🍺

[ramsey]

Due to BC issues, I have reverted the actions/cache upgrade in version 2.3.1 and have released 3.0.0, which includes the actions/cache upgrade. Please update your pinned versions to 3.0.0. See discussion on #252, for more info.