Describe the bug
The assign milestone workflow was created to assign milestones when PRs are merged and no milestone was set. It used pull_request_target, so it knew what branch it was targeting, and used the version file to find the milestone.
GitHub changed the behavior for pull_request_target, in effect since December 8 2025, to always use the default branch for the workflow, and set the GITHUB_REF and GITHUB_SHA according to the default branch (main here).
https://github.blog/changelog/2025-11-07-actions-pull_request_target-and-environment-branch-protections-changes/
So the approach that was used doesn't work anymore. A different approach is needed,
Describe the bug
The assign milestone workflow was created to assign milestones when PRs are merged and no milestone was set. It used pull_request_target, so it knew what branch it was targeting, and used the version file to find the milestone.
GitHub changed the behavior for pull_request_target, in effect since December 8 2025, to always use the default branch for the workflow, and set the
GITHUB_REFandGITHUB_SHAaccording to the default branch (main here).https://github.blog/changelog/2025-11-07-actions-pull_request_target-and-environment-branch-protections-changes/
So the approach that was used doesn't work anymore. A different approach is needed,