[CI] Move to the latest release of the get-release action

[NlightNFotis]

The get-release action at version 1 has now been deleted, and as a result our latest release package building errors out with "unable to find version 1".

This should fix the problem.

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[codecov]

Codecov Report

Base: 78.03% // Head: 78.03% // No change to project coverage 👍

Coverage data is based on head (446b00c) compared to base (ab2b0cb).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #7279   +/-   ##
========================================
  Coverage    78.03%   78.03%           
========================================
  Files         1624     1624           
  Lines       187405   187405           
========================================
  Hits        146249   146249           
  Misses       41156    41156           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[tautschnig]

This is surprising to me: isn't this what you get by default (assuming 1.3.2 is the most recent version of v1)?

[NlightNFotis]

Hi Michael, sorry for late response:

This ended up being needed - I'm not entirely sure why though. There appear to be multiple reports in other projects as well, for instance -> actions/setup-node#211

I think what happens is that there's two levels of tags that need to have a close correspondence for the shorthand version to work. It may be that the author of this action made a mistake and broke that correspondence between the tags, and this is why the version wasn't being found when it was looked up in a registry by GitHub Actions.

But this is me speculating based on the fix, other reports and some documentation - I'm not entirely sure about the root cause.