Mark CBMC version 5.62.0

[NlightNFotis]

• 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.

[tautschnig]

Can you please hold back as I'd like to have a regression fix included that I'm about to PR.

[tautschnig]

Can you please hold back as I'd like to have a regression fix included that I'm about to PR.

That PR is #7020.

[NlightNFotis]

@tautschnig, Yep, happy to wait - feel free to unblock this when you're ready.

[codecov]

Codecov Report

Merging #7019 (fadd71c) into develop (d5462fb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #7019   +/-   ##
========================================
  Coverage    77.88%   77.88%           
========================================
  Files         1569     1569           
  Lines       180891   180891           
========================================
  Hits        140878   140878           
  Misses       40013    40013           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4a2ab0...fadd71c. Read the comment docs.

[tautschnig]

#7020 is now merged, if you could please rebase then I'd be happy for this release to proceed.

[thomasspriggs]

#7020 is now merged, if you could please rebase then I'd be happy for this release to proceed.

I don't think we even need to rebase. If I remember correctly we normally tag the merge commit as the release, which will include any other changes merged to develop.

[NlightNFotis]

Yeah, I don't think we need to rebase (as there are no conflicts in the files edited), but I have issued a re-run of the failed jobs (given that they are required).