[bre-1628] cherry-pick release workflow change

[aj-bw]

🎟️ Tracking

bre-1628

📔 Objective

We want to temporarily remove the draft: true key for testing release process enhancements for the next release. This key being passed results in the git tag not being created until we go and manually publish the draft GH release, meaning the following publish workflow will fail.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Checkmarx One – Scan Summary & Details – 3ebea89c-9de5-4b73-9885-3a9b10c08ce6

Great job! No new security vulnerabilities introduced in this pull request

[vgrassia]

What about the release notes? Is the plan to edit them directly after the release is published?

[aj-bw]

What about the release notes? Is the plan to edit them directly after the release is published?

@vgrassia Yes that is the plan. this is more so a stop gap for this next release only, next sprint I will improve it to retrieve the release notes from the card and pass it to the workflow.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.48%. Comparing base (b633ad7) to head (ff647ec).
⚠️ Report is 1 commits behind head on rc.

Additional details and impacted files

@@            Coverage Diff             @@
##               rc    #7023      +/-   ##
==========================================
+ Coverage   56.24%   56.48%   +0.23%     
==========================================
  Files        1982     2002      +20     
  Lines       87669    88314     +645     
  Branches     7820     7892      +72     
==========================================
+ Hits        49313    49887     +574     
- Misses      36526    36586      +60     
- Partials     1830     1841      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.