Add Changelog verifier workflow

[owaiskazi19]

Description

Add Changelog verifier workflow for creating release notes faster

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[kaituo]

So this will allow creating changelog every time merge a PR?

[owaiskazi19]

So this will allow creating changelog every time merge a PR?

Yes, devs need to add an entry into the CHANGELOG file every time they create a PR otherwise the CHANGELOG github action would fail.
For example this changelog entry was added with the bug fix.

Next time while creating the release notes all the entries can be copied directly to the release notes and can be deleted from either 2.x or 3.0 section as a clean up.
Example: https://github.com/opensearch-project/flow-framework/pull/1036/files

If for changes we don't need to add an entry for such PRs we can add skip-changelog label, that would pass the changelog workflow

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.55%. Comparing base (d4ce6cf) to head (4e0877a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1413      +/-   ##
============================================
- Coverage     81.56%   81.55%   -0.02%     
- Complexity     5856     5860       +4     
============================================
  Files           533      533              
  Lines         23664    23664              
  Branches       2374     2374              
============================================
- Hits          19302    19299       -3     
- Misses         3197     3204       +7     
+ Partials       1165     1161       -4     

Flag	Coverage Δ
plugin	81.55% <ø> (-0.02%)	⬇️

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

see 9 files with indirect coverage changes

[kaituo]

So this will allow creating changelog every time merge a PR?

Yes, devs need to add an entry into the CHANGELOG file every time they create a PR otherwise the CHANGELOG github action would fail. For example this changelog entry was added with the bug fix.

Next time while creating the release notes all the entries can be copied directly to the release notes and can be deleted from either 2.x or 3.0 section as a clean up. Example: https://github.com/opensearch-project/flow-framework/pull/1036/files

If for changes we don't need to add an entry for such PRs we can add skip-changelog label, that would pass the changelog workflow

Can you document the process in https://github.com/opensearch-project/anomaly-detection/blob/main/DEVELOPER_GUIDE.md ?

[owaiskazi19]

@kaituo BWC failure looks similar to opensearch-project/OpenSearch#15234. Is this safe to merge?