feat: Automate Triggering of trigger-release.sh After Init Release GitHub Action #20323

[jaehanbyun]

Closes: #20323

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

What I have done:

According to the existing documentation, in Step 2 - Tag Release Branch of the release process, developers are required to manually execute the trigger-release.sh script. This manual step introduces the potential for human error, such as entering the wrong version number or working on the incorrect branch.

To mitigate these risks, I have automated this step by adding a new job called trigger-release to the init-release.yaml workflow. This job automatically executes the trigger-release.sh script after the prepare-release job completes. By doing so, the release process becomes fully automated, eliminating the need for manual script execution and reducing the likelihood of human errors.

[bunnyshell]

❗ Preview Environment undeploy from Bunnyshell failed

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to try again to remove the environment

[pasha-codefresh]

It should be executed after init-release PR is merged

[jaehanbyun]

I have created a new workflow file. PTAL!

[pasha-codefresh]

Thank you @jaehanbyun for taking it, left small comment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (master@29d5229). Learn more about missing BASE report.
Report is 10 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master   #20560   +/-   ##
=========================================
  Coverage          ?   55.12%           
=========================================
  Files             ?      324           
  Lines             ?    55116           
  Branches          ?        0           
=========================================
  Hits              ?    30384           
  Misses            ?    22114           
  Partials          ?     2618           

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

[pasha-codefresh]

Thank you, from first glance it looks good, lets discuss it on contribution meeting, and probably we will merge it after 2.13 GA release

Also @34fathombelow should review it

[34fathombelow]

LGTM, only nit is to update the release docs and mention that Step 2 is now automated.
https://github.com/argoproj/argo-cd/blob/master/docs/developer-guide/releasing.md

[andrii-korotkov-verkada]

@pasha-codefresh, do you still have concerns about this PR?

[jaehanbyun]

@pasha-codefresh, Could you please confirm once again if this PR can now be merged?

[pasha-codefresh]

We just need test it on fork and make sure that it works properly