-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release automation #2062
Release automation #2062
Conversation
Add a GitHub Actions workflow that creates a new draft release ready for publishing.
Add a comment for automation to use to insert the next release.
Add a GitHub Actions workflow that closes the current milestone and creates a pull request to update the samples and release notes.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2062 +/- ##
==========================================
+ Coverage 83.67% 83.69% +0.01%
==========================================
Files 312 312
Lines 7106 7114 +8
Branches 1054 1054
==========================================
+ Hits 5946 5954 +8
Misses 789 789
Partials 371 371
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This is amazing @martincostello👍 I was silently hoping we could automate this at some point. |
Move any entries in the Unshipped public API files to their corresponding Shipped file.
Move the inline PowerShell to script files.
Tested with these PRs in a copy of the repo: |
This PR aims to add some GitHub Actions automation to streamline the release process and some of the boring tasks associated with it.
I'm going to test these out in a throwaway repo before merging to check they work as intended.
release
with the version number to publish as (e.g.8.3.2
) will create a new draft release for that tag with the release notes populated. Then the person running it can click through to the link to the draft to check they're happy with the content before publishing it, which kicks off the release workflow to publish the packages to NuGet.org after the tag is created.MinVerMinimumMajorMinor
is still a manual process if we want to increase the minor or major version of Polly itself.PublicAPI.Unshipped.txt
files to the correspondingPublicAPI.Shipped.txt
file.