Release CI completes without the test suite

[bruno-garcia]

Release 2.2.1 went out.
The release/2.2.1 branch didn't seem to run the tests:

https://github.com/getsentry/sentry-unity/actions/runs/11335211101

[bruno-garcia]

Seems related to:

• Releases cause 2 branches to be created (CI runs then twice) #1845

The release with version version has the full CI run:

• https://github.com/getsentry/sentry-unity/actions/runs/11263831196
  

The release with release/version doesn't:

• https://github.com/getsentry/sentry-unity/actions/runs/11261339740
  

Also note the two different bots involved

[bitsandfoxes]

For context: This was done intentionally. The idea was: If main is green it should not take two hours for a release to go through. But as the team is growing we should rethink such a "by convention" processes.

[bruno-garcia]

For context: This was done intentionally. The idea was: If main is green it should not take two hours for a release to go through. But as the team is growing we should rethink such a "by convention" processes.

I see, that makes sense. But do we have safeguards to make sure the build from the branch (not just main) that we're releasing from is green and hence the release build doesn't need CI?

Also, even package validation doesn't run? If we make any mistake during the release flow (bumping versions, etc) no visibility

[bitsandfoxes]

Also, even package validation doesn't run?

Build and Package Validation are part of the Release run.