Regression - Gitlab release evidence not being collected if release is created via UI

Summary

(Summarize the bug encountered concisely)

Users reported a regression where Release evidence is not generated consistently when you create a release from a tag in the UI.

Steps to reproduce

(How one can reproduce the issue - this is very important)

  1. Go to Project > Project Overview > Releases
  2. Click Create a Release button
  3. Fill out relevant release details
  4. Navigate to the created Release and see if Evidence has been collected

What is the current bug behavior?

(What actually happens)

Evidence is NOT collected

What is the expected correct behavior?

(What you should see instead)

Evidence is collected

Implementation

  • Do not send released_at unless it is specified by the user - !96183 (merged)
  • Check for Release Evidence in feature spec - !95748 (merged)
  • Update docs to mention that released_at should only be specified when creating a historical or upcoming Release - !97177 (merged)
Edited by Alishan Ladhani