Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[repo] Release process tweaks & improvements 4 #5598

Merged
merged 46 commits into from May 13, 2024

Conversation

CodeBlanch
Copy link
Member

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: CodeBlanch#36

Merge requirement checklist

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

@CodeBlanch CodeBlanch added the infra Infra work - CI/CD, code coverage, linters label May 8, 2024
@CodeBlanch CodeBlanch requested a review from a team as a code owner May 8, 2024 06:24
Copy link

codecov bot commented May 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

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

Additional details and impacted files

Impacted file tree graph

@@            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
Copy link
Contributor

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

@CodeBlanch
Copy link
Member Author

@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" 🤣

image

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

.markdownlint.yaml Outdated Show resolved Hide resolved
@CodeBlanch CodeBlanch merged commit 9d12b36 into open-telemetry:main May 13, 2024
43 checks passed
@CodeBlanch CodeBlanch deleted the repo-release-tweaks4 branch May 13, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra Infra work - CI/CD, code coverage, linters
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants