Update release description with CHANGELOG and upload an artifact with every build.

[dblock]

Description

Update release description with CHANGELOG, and upload an artifact with every build.

Before:

After:

https://github.com/dblock/opensearch-api-specification/releases/tag/release-permalink-latest

Also uploads the build artifacts to the workflow run so it can be downloaded with a permalink if needed.

Issues Resolved

Closes #380.

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.

[github-actions]

Changes Analysis

Commit SHA: 4e19a1c
Comparing To SHA: 046b7d1

API Changes

Summary

NO CHANGES

Report

The full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/9880051401/artifacts/1688047199

API Coverage

	Before	After	Δ
Covered (%)	483 (47.31 %)	483 (47.31 %)	0 (0 %)
Uncovered (%)	538 (52.69 %)	538 (52.69 %)	0 (0 %)
Unknown	24	24	0

[Xtansia]

I'm happy for this to be merged for now and to just re-visit it later, but I have some opinions:

I'm not super convinced on the value add of the build artifact compared to what's already associated with the release given it's not a true permalink and the only way to map the non-latest commit to an artifact is to query via the actions API.

I also thinks there's an opportunity to clean this workflow up as the automatic gh release action is now unmaintained and editing the release message in multiple steps seems error prone.

[dblock]

I'm not super convinced on the value add of the build artifact compared to what's already associated with the release given it's not a true permalink and the only way to map the non-latest commit to an artifact is to query via the actions API.

True. If nobody uses it we can delete it in the next iteration.

I also thinks there's an opportunity to clean this workflow up as the automatic gh release action is now unmaintained and editing the release message in multiple steps seems error prone.

Yes indeed. Amazingly there's no action that exists that lets you create a release with the description right away. It might actually not be possible? ;)