Stop filtering out PRs that were also backported to previous versions

[florent-leborgne]

This PR:

• /!\ is co-authored using AI
• updates the logic of the tool so that PRs released in multiple versions show for each version they were released in instead of being filtered out
• adds a safeguard warning when a PR has several labels belonging to the same minor version as in this case we need to check that it has not been released in a previous patch of that same minor
• removes the step for selecting unreleased versions

Tested locally to check that the updated behaviour works as expected ✅:

• for any given selected/specified stack version for kibana/security/endpoint/obs, the right PRs are retrieved regardless of other versions they might have been backported to as well
• serverless release notes look unaffected by these changes

Fixes: #50
Fixes the behavior raised in https://elastic.slack.com/archives/C0JF80CJZ/p1763136763466579

[florent-leborgne]

@Ikuni17 could you take a look? 🙏

[bmorelli25]

Awesome sauce! A couple comments. Note: I did not test this PR.

Can you update the documentation in https://github.com/elastic/kibana-release-notes/blob/d1ab661cd05ccabaa5a5607bef137c1198d580ba/src/pages/release-notes/wizard.tsx#L326-327

[florent-leborgne]

Can you update the documentation in https://github.com/elastic/kibana-release-notes/blob/d1ab661cd05ccabaa5a5607bef137c1198d580ba/src/pages/release-notes/wizard.tsx#L326-327

Actually I've removed this wizard step as it is not useful with the new expected behavior in my latest commit

[lcawl]

My concern would be if this change makes the Kibana release notes have different behaviour than the other products' docs. [edit] It looks like Elasticsearch is following this same pattern, e.g. I see that elastic/elasticsearch#137222 appears in the 9.1.7 and 9.2.1 sections of https://www.elastic.co/docs/release-notes/elasticsearch, as well as in https://www.elastic.co/guide/en/elasticsearch/reference/8.19/release-notes-8.19.7.html

I wondered how this overlapped with the exclusion of PRs that have backport labels per

kibana-release-notes/src/config/templates/kibana.ts

Line 6 in d1ab661

excludedLabels: ['release_note:skip', 'Team:Docs', 'reverted', 'backport'],

... but after a quick test locally with a PR like elastic/kibana#242691 it does show up in the 9.1.8 release notes (but its backport PR elastic/kibana#242721 does not), which I think is working as hoped.

[florent-leborgne]

@lcawl it's been consistently requested for multiple teams. I think ES does it, and even for Kibana/solutions we've been doing it as well (or trying to as it appears we missed some PRs) for some months.

I wondered how this overlapped with the exclusion of PRs that have backport labels

This is still the desired behavior - as PRs with the backport labels will have an original PR with the actual labels that we need for the tool (release_note:category, team/feature labels, version labels), while backport PRs don't.
This PR here doesn't change this

[Ikuni17]

Thanks for doing this, nice work! I was always confused about picking those extra versions and wanted to fix this.

I pushed a few small commits to refactor and add tests
abec88e...cc2052f

I ran everything locally and LGTM. If you could quickly rerun my changes locally incase I missed something and then merge.

[florent-leborgne]

Thank you @Ikuni17!! Tested locally and works fine.

I think I lost some permissions on this repo as I'm not able to trigger the CI nor merge or select reviewers.

If you don't mind doing it for me or @lcawl if you still can. :)

[Ikuni17]

Admin merging, CI passed here: https://github.com/florent-leborgne/kibana-release-notes/actions/runs/19450049965