Conditionally override version after cutting a release branch

[kenodegard]

Description

The first canary build created after cutting a release branch produces a misleading version/build string. Instead of deriving the version/build string from the upcoming release, it uses the version from the most recent release on main. This leads to a race condition with packages produced by the canary build workflow from the main branch.

The race condition occurs because both main and the release branch end up generating packages with the same version/build string. Even though we upload them to anaconda.org with different labels, only one package would "win." As a result, we occasionally see the package first appear under one label, only to disappear and reappear under the other label when the other canary build workflow finishes and uploads it's packages.

The proposed fix is to override the default behavior of git describe --tag when no releases have been made on the branch yet.

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[codspeed-hq]

CodSpeed Performance Report

Merging #5483 will not alter performance

_{Comparing kenodegard:recipe-version-override (414d2f9) with main (adfdc2a)}

Summary

✅ 3 untouched benchmarks