[RELEASES] Only tag 2.x line as latest when making releases

[SebastianThorn]

Describe the bug

https://github.com/opensearch-project/OpenSearch/releases says that 1.3.17 is the latest release, this is somewhat correct, but not really.

2.14.0 Should be tagged as latest.

Related component

Other

To Reproduce

https://github.com/opensearch-project/OpenSearch/releases

Expected behavior

https://github.com/opensearch-project/OpenSearch/releases to point to latest version

Additional Details

No response

[dblock]

GitHub "latest" by default means chronologically latest. It does look like it's possible to no mark releases as lates when they are published (cli/cli#2678 (comment)) so we could probably avoid marking 1.3.x line as "latest" in build/release scripts.

@prudhvigodithi do you know where to make this change? @SebastianThorn care to help?

[SebastianThorn]

@dblock Hi, I had the same issue with Harbor and their RC-builds, and they did something with their release.

goharbor/harbor#20248 there are 2 links in that issue that might be of help, I'm not very good at github-centric things.

Br Sebastian Thörn

[prudhvigodithi]

Hey @SebastianThorn let me check the link you shared, today for the the OpenSearch repo AFAIK the release is done by the automation used here https://github.com/opensearch-project/OpenSearch/blob/main/.github/workflows/auto-release.yml, coming from https://github.com/ncipollo/release-action looks like we can use makeLatest to false for 1.3 series workflow https://github.com/opensearch-project/OpenSearch/blob/1.3/.github/workflows/auto-release.yml.
@getsaurabh02 @peterzhuamazon.

[dblock]

Thanks @prudhvigodithi, @SebastianThorn want to PR the change into the 1.x and 1.3 branches?

[andrross]

[Triage - attendees 1 2 3 4 5]

Thanks for filing.