Update release notes ID format for automated URL generation

[leemthompo]

Summary

We need to update the format of IDs in our release notes to support automated URL generation in GitHub release pages.

Description

We learned that automated URLs in GitHub release pages (such as https://github.com/elastic/elasticsearch/releases/tag/v9.0.0) require our IDs to be of the form X.x.x.

See https://github.com/elastic/unified-release/pull/2364 for the format required by the release team.

Required changes

• Update the ID format in release notes from #foo-901-release-notes to #foo-9.0.1-release-notes
• This change enables the release team to auto-generate URLs with each commit using their <MINOR_VERSION> variable
  • Reference: https://github.com/elastic/unified-release/pull/2364

Example

Current format:
#elasticsearch-901-release-notes

New format:
#elasticsearch-9.0.1-release-notes

Priority

This should be implemented for the upcoming 9.0.1 release and all future releases.

Note

We don't need to retroactively update the 900 ids

Folks concerned

Borrowed from docs release 😝

Product	Assignees	Updated
Docs eng	@elastic/docs-engineering	TODO
APM Server	@elastic/obs-ds-intake-services	✅
Beats	@kilfoyle	✅
Elasticsearch	@brianseeders	✅
Elasticsearch Hadoop	@jbaiera	TODO
Elasticsearch Java Client	@l-trotta	TODO
Elasticsearch JavaScript Client	@JoshMock	✅
Elasticsearch .NET Client	@flobernd	TODO
Elasticsearch PHP Client	@ezimuel	TODO
Elasticsearch Python Client	@pquentin	TODO
Elasticsearch Ruby Client	@picandocodigo	TODO
Fleet & Agent	@kilfoyle	✅
Kibana	@florent-leborgne @wajihaparvez	✅
Logstash	@kaisecheng	✅
Observability	@KOTungseth	✅
Security	@nastasha-solomon	✅

[leemthompo]

Warning

If the following aren't updated, GitHub release pages and their auto-generated emails will 404, which happened for 9.0.0.

This is time sensitive for the following products as they have these autogenerated links:

• Elasticsearch
• Kibana
• APM-Server
• Beats
• Elastic-Agent
• Elasticsearch-Hadoop
• Logstash

But it would make sense for everybody to align here going forward ASAP :)

[nastasha-solomon]

Thanks for filing this, @leemthompo. I'm updating Security's release notes templates to enforce this new versioning format moving forward.

[JoshMock]

I believe elasticsearch-js is all fixed up with the right IDs now.

[leemthompo]

@belimawr would you know who handles this for Beats?

[florent-leborgne]

Will be ok for Kibana ✅

[leemthompo]

thanks to @kaisecheng for jumping on a hot fix for logstash before 9.0.1 release :)

[kaisecheng]

@leemthompo Thanks so much for taking care of Logstash doc release. This is the PR to update the ID format of release note auto generation

[carsonip]

APM Server ID format should be covered by elastic/apm-server#16817

However, I don't think the apm server id change will have any effect at all because https://github.com/elastic/unified-release/pull/2364 links to observability changelog instead of elastic apm changelog . Is it expected?

[leemthompo]

@carsonip I guess that was a typo, @alpar-t I'll open an issue to update the APM release notes link to https://www.elastic.co/docs/release-notes/apm#<MINOR_VERSION>-release-notes

[carsonip]

@carsonip I guess that was a typo, @alpar-t I'll open an issue to update the APM release notes link to https://www.elastic.co/docs/release-notes/apm#<MINOR_VERSION>

Right, judging by the current structure and the new ID format, 9.0.1 will be at https://www.elastic.co/docs/release-notes/apm#elastic-apm-9.0.1-release-notes

[belimawr]

@belimawr would you know who handles this for Beats?

@leemthompo, I was on PTO, I'm only seeing it now. It seems Beats is already done, but let me know if more help is needed.