Remove changelog infrastructure in favor of centralized release notes automation#11563
Remove changelog infrastructure in favor of centralized release notes automation#11563ananzh wants to merge 1 commit intoopensearch-project:mainfrom
Conversation
… automation Signed-off-by: Anan Zhuang <ananzh@amazon.com>
|
Do we need to remove the Changelog bot? |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11563 +/- ##
=======================================
Coverage 61.58% 61.58%
=======================================
Files 4995 4995
Lines 137542 137542
Branches 23901 23901
=======================================
Hits 84707 84707
+ Misses 46692 46691 -1
- Partials 6143 6144 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@ananzh Should we test out the other opensearch-build team's centralized bot first , before removing the current system. Else it might be be too much work later to update the CHANGELOG file |
Description
Remove the OSD-specific changelog workflow and fragment system, which was unique among all 160 opensearch-project repositories. Release notes will now be generated automatically by the opensearch-build team's centralized bot using PR labels and commit history. This cleanup eliminates manual changelog maintenance while standardizing the release notes process across the organization.
Issues Resolved
NA
Screenshot
NA
Testing the changes
NA
Changelog
Check List
yarn test:jestyarn test:jest_integration