[repo] Release process tweaks & improvements 4

[CodeBlanch]

Changes

• Adds a new workflow prepare-release.yml which automates/streamlines the following tasks in the release process:
  • Automatically open a PR to update CHANGELOGs and public api files (stable releases only) for the tag being released
  • Once that PR is merged (by a maintainer) you can interact with the workflow\bot and reply with a comment containing "/CreateReleaseTag" in the body to instruct the workflow\bot to create the tag and then kick off the package workflow which...
    • Creates packages as artifacts on the workflow
    • Creates draft release for when packates have been uploaded
    • Creates post-release props update PR (stable releases only)

Example

Here is a test run of the process: https://github.com/CodeBlanch/opentelemetry-dotnet/pull/36

Merge requirement checklist

• [X] CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.55%. Comparing base (6250307) to head (125a3ce). Report is 219 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5598      +/-   ##
==========================================
+ Coverage   83.38%   85.55%   +2.16%     
==========================================
  Files         297      265      -32     
  Lines       12531    11337    -1194     
==========================================
- Hits        10449     9699     -750     
+ Misses       2082     1638     -444     

Flag	Coverage Δ
unittests	?
unittests-Solution-Experimental	85.71% <ø> (?)
unittests-Solution-Stable	85.73% <ø> (?)
unittests-Unstable-Core	19.85% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 113 files with indirect coverage changes

[TimothyMothra]

Are there restrictions on who can comment with the "/CreateReleaseTag" ?

[CodeBlanch]

@TimothyMothra Good question! Yes. What I did is have the bot lock the PR. While locked only collaborators of the repo may comment which limits who can speak "/CreateReleaseTag" 🤣

The bot will ignore "/CreateReleaseTag" if the PR isn't locked when it is posted.