Repository navigation
GitHub pull_request_target changes affect the official images job #2686
Description
Expected Behavior
official-images.yml produces a PR and comment on the triggering PR.
Current Behavior
Because of the upcoming changes to this trigger, the latest push for the v27 image failed to create the upstream PR
https://github.com/nodejs/docker-node/actions/runs/42901790243/workflow
Activity
nschonni commentedon Nov 10, 2026
Failure on that job was actually unrelated, and caused by a
chmodchange, but action is likely still required for thepull_request_targetchangenschonni commentedon Nov 10, 2026
Created a ruleset https://github.com/nodejs/docker-node/settings/actions/rules/12921
Leaving this open till after December 2nd, to see if it "worked".
Likely will be tested by fixing the
chmodissue in a new PR.MikeMcC399 commentedon Nov 11, 2026
I approved and merged #2687
That caused docker-library/official-images#22729 to be created with the non-matching title
which I can't correct, since the PR was created by https://github.com/nodejs-github-bot, so I just left a comment there.
Viewing https://github.com/nodejs/docker-node/settings/actions/rules/insights and seeing that there are no new instances of "Would block" makes me think that your new rule creation was successful.
https://github.blog/changelog/2026-11-02-pull_request_target-blocked-by-default-december-2/ was the change log article referring to the cut-over Dec 2, 2026.
Probably this can be closed now since https://github.com/nodejs/docker-node/actions/runs/42984797639 caused no error or remark.