Description

nschonni

opened on Nov 10, 2026

Issue body actions

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

Possible Solution

Steps to Reproduce

Additional Information

Activity

1. nschonni commented on Nov 10, 2026

   

   nschonni

   on Nov 10, 2026

   MemberAuthor

   More actions

   Failure on that job was actually unrelated, and caused by a chmod change, but action is likely still required for the pull_request_target change
2. nschonni commented on Nov 10, 2026

   

   nschonni

   on Nov 10, 2026

   MemberAuthor

   More actions

   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 chmod issue in a new PR.
3. MikeMcC399 commented on Nov 11, 2026

   

   MikeMcC399

   on Nov 11, 2026

   Contributor

   More actions

   I approved and merged #2687

   That caused docker-library/official-images#22729 to be created with the non-matching title

   Node: fix: add back chmod 755 to Stackbrew
   

   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.
4. MikeMcC399

   added

   build process

   on Nov 12, 2026

Issue actions