[ahus1]

Closes #97

Replaces the labeller workflow of keycloak/keycloak that relied on pull_request_target, which GitHub is phasing out.

Decisions and assumptions:

• The label is derived from the target branch: a PR merged into main gets the next minor after the highest release/X.Y branch, a PR merged into release/X.Y gets the next micro after the highest X.Y.* tag.
• 26.9.0 is mapped to 27.0.0, as there will be no more 26.x minor release after 26.8.
• Issues are taken from the PR description, falling back to the merge commit message, using the same parser as the backport linking; references to other repositories are ignored.
• Referenced pull requests and missing issues are skipped, the remaining issues are still labeled.
• The backport/ label of the target branch is removed, other backport/ labels stay.
• The release/ label is created with the color used in keycloak/keycloak if it doesn't exist yet.
• The app needs the Pull request event, plus read access to pull requests and contents, and write access to issues.

Tested with a test GitHub App on a fork, each scenario creating a new release/ label:

• Merged into main with a release/26.5 branch present: Test #98 (A): main, new label, skipped refs ahus1/keycloak#468 references a missing issue, a pull request and the issue Test #98 (A): main, new label, skipped refs ahus1/keycloak#467. Only the issue got release/26.6.0 and lost backport/main; the pull request was left untouched.
• Merged into release/26.4 with the tags 26.4.0, 26.4.2 and 26.4.3: [26.4] Test #98 (B): release branch, new label ahus1/keycloak#470 closing [26.4] Test #98 (B): release branch, new label ahus1/keycloak#469 got release/26.4.4 and lost backport/26.4.
• Closing keyword only in the merge commit message: [26.4] Test #98 (C): commit message fallback ahus1/keycloak#472 labeled [26.4] Test #98 (C): commit message fallback ahus1/keycloak#471 with release/26.4.4.

[Copilot]

🟡 Changes recommended

Release-labeling bugs can misparse references, modify pull requests instead of issues, and abort valid issue updates when references are missing or label creation races.

5 open issues

• Fetch only branch or tag data needed for the target branch · New
• Handle concurrent release-label creation safely · New
• Continue when a referenced issue is missing · New
• Skip pull requests when updating referenced issues · New
• Reuse the existing closing-issue parser · New

What changed in this PR

Moves merged-PR release labeling into the bot, replacing the workflow that relied on pull_request_target and addressing #97.

Changes:

• Derives release labels from target branches and tags, including the 26.9.0 → 27.0.0 mapping.
• Labels same-repository issues referenced in the PR description or merge commit and removes the target branch’s backport label.
• Adds utility tests and documents the new behavior.

File	Description
src/​test/​java/​org/​keycloak/​gh/​bot/​utils/​ReleaseLabelsTest.java	Tests version selection and issue-reference parsing.
src/​main/​java/​org/​keycloak/​gh/​bot/​utils/​ReleaseLabels.java	Calculates release labels and extracts issue references.
src/​main/​java/​org/​keycloak/​gh/​bot/​utils/​Labels.java	Exposes repository label-existence checks.
src/​main/​java/​org/​keycloak/​gh/​bot/​AddReleaseLabelOnMerge.java	Handles merged PRs and updates issue labels.
README.md	Documents release labeling on merge.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

An unnecessary merge-commit fetch adds a GitHub API request and makes labeling depend on its success even when the PR description already contains closing references.

1 open issue

• Fetch merge commit only when description has no issue references · New

5 resolved since last review

• Reuse the existing closing-issue parser
• Skip pull requests when updating referenced issues
• Continue when a referenced issue is missing
• Handle concurrent release-label creation safely
• Fetch only branch or tag data needed for the target branch

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues remain for the release-labeling change.

No open issues 🎉

1 resolved since last review

• Fetch merge commit only when description has no issue references

_{Review effort: Balanced}