-
-
Notifications
You must be signed in to change notification settings - Fork 229
chore: Enable automatic release management #4818
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4818 +/- ##
=======================================
Coverage 73.86% 73.86%
=======================================
Files 483 483
Lines 17577 17577
Branches 3464 3464
=======================================
+ Hits 12983 12984 +1
+ Misses 3741 3740 -1
Partials 853 853 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| scripts\build-sentry-cocoa.sh = scripts\build-sentry-cocoa.sh | ||
| scripts\update-project-xml.ps1 = scripts\update-project-xml.ps1 | ||
| scripts\build-sentry-native.ps1 = scripts\build-sentry-native.ps1 | ||
| scripts\ios-simulator-utils.ps1 = scripts\ios-simulator-utils.ps1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea where this is coming from. The file doesn't appear to exist in the repo so seems OK to remove it from the solution file (which is generated in any case).
We frequently run into merge coflicts on the
CHANGELOG.mdfile, so we're trying automatic changelog management.I copied the initial
release.ymlfile from the Python repo and then tweaked this to match how we've historically done change logs in this repo.For this to work, we also need to consider the automatic changelog generation that happens when Updater runs to update dependencies. Unfortunately it seems the only option there is to either enable or disable changelog generation for new PRs. I've disabled it then.
Tip
Perhaps later we can circle back to use the original script that was used to generate changelog entries somehow in conjunction with the automatic changelog management.
#skip-changelog