René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"PRs updates may cause unwanted PR creation in `docker-library/official-images`","articleBody":"## Situation\n\nWhen `Dockerfile-template.*` changes are made and `Dockerfile` updates in the release line directories are also made, then the repo automatically triggers a PR to build a new release. The workflow [official-pr](https://github.com/nodejs/docker-node/blob/main/.github/workflows/official-pr.yml) is responsible for this.\n\nUnless the update is part of a new release, then `Dockerfile` updates should generally not be done manually. These updates should be left to the automated processes that are triggered when the repo's [automatic-updates.yml](https://github.com/nodejs/docker-node/actions/workflows/automatic-updates.yml) polling workflow detects a new Node.js release.\n\n## Suggestion\n\nResearch the background and add instructions to the [CONTRIBUTING](https://github.com/nodejs/docker-node/blob/main/CONTRIBUTING.md) document about when `Dockerfile` updates should be made directly, and when it should be left to automation.\n\nFor those cases where no direct `Dockerfile` update should be included in a PR, describe also how to test such PRs.","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-07-12T14:26:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/2564/docker-node/issues/2564"}