Hi,

>From November 2026 the pull_request_target event is disabled for ASF
repositories [1], so I'm migrating our shared workflows in
maven-gh-actions-shared (v5) [2].
Tracking issue: [3].

PR Check (license declaration in the PR description)
- It is now triggered by workflow_run after a new, minimal PR Signal
workflow (pull_request).
- The result is shown on the PR as the commit status PR Check /
license-declaration.
- PR Signal must be present on every branch PRs are opened against,
including maintenance branches.
- Workflows of PRs from external contributors must be approved, so the
status shows up only after approval.
- Already migrated: maven (including the 4.0.x / 3.10.x / 3.9.x
branches), maven-surefire, maven-enforcer, maven-invoker-plugin,
maven-site.
- The setup is described in the README [4].

PR Automation (milestone / assignee / labels after merge)
- It can now be triggered by push to the listed branches and finds the
merged PR by its merge commit. The old pull_request_target: closed
keeps working during the transition.
- In push mode a PR closed without merge is not handled, since no push happens.
- Tested on maven-toolchains-plugin, which is already switched to push.
- The current documentation [5] still shows pull_request_target. It
will be updated for push.

I'll migrate the remaining repositories step by step.
If you see anything unexpected, a missing status or a failed run,
please comment on the issue or let me know.

[1] https://infra.apache.org/github-actions-policy.html
[2] https://github.com/apache/maven-gh-actions-shared/tree/v5
[3] https://github.com/apache/maven-gh-actions-shared/issues/334
[4] https://github.com/apache/maven-gh-actions-shared#pr-check
[5] https://github.com/apache/maven-gh-actions-shared#pull-request-automation

-- 
Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to