GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — chore: update messages on automated/official PRs by nschonni · Pull Request #2665 · nodejs/docker-node

Conversation

@nschonni

@nschonni nschonni commented Oct 21, 2026

Copy link
Copy Markdown
Member

Description

Adds the pointers/messages about the Docker Image release cycle to the body of the PRs.

Motivation and Context

Probably won't prevent the "why isn't this available" comments we often get, but having it in the body means it's less likely to ge folder/hidden if people come to the actual PRs to comment.

Testing Details

Example Output(if appropriate)

Types of changes

  • Documentation
  • Version change (Update, remove or add more Node.js versions)
  • Variant change (Update, remove or add more variants, or versions of variants)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (none of the above)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • All new and existing tests passed.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@nschonni
nschonni force-pushed the pr-body-updates branch from efa8cba to 78941b5 Compare October 21, 2026 20:24
@nschonni
nschonni requested a review from a team October 21, 2026 20:25
MikeMcC399
MikeMcC399 reviewed Oct 22, 2026
View reviewed changes
Comment thread .github/workflows/official-pr.yml Outdated
issue-number: ${{ github.event.pull_request.number }}
body: |
Created PR on the official-images repo (${{ steps.create-pr.outputs.pull-request-url }}). See https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what if you are wondering when it will be available on the Docker Hub.
Created PR on the official-images repo (${{ steps.create-pr.outputs.pull-request-url }}).

@MikeMcC399 MikeMcC399 Oct 22, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's necessary to remove this link.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
MikeMcC399
MikeMcC399 reviewed Oct 22, 2026
View reviewed changes
Comment thread .github/workflows/automatic-updates.yml Outdated
base: main
commit-message: 'feat: Node.js ${{ steps.updt.outputs.result }}'
title: 'feat: Node.js ${{ steps.updt.outputs.result }}'
body: 'Before commenting to ask when this will be available, see the [README](https://github.com/nodejs/docker-node#release-availability)'

@MikeMcC399 MikeMcC399 Oct 22, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would have worded this a bit differently, but that's more of a style question.

"If you are reading this PR soon after it has been merged, you may find that new Docker images are missing or appear broken. Check back later and see the README for background information."

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@nschonni nschonni Oct 22, 2026

Copy link
Copy Markdown
Member Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to suggest the wording, I don't really feel strongly about the words I used

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@MikeMcC399 MikeMcC399 Oct 27, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to get back to this topic at a more general level in terms of how we can better inform users about progress and I'd like to involve the Docker team for this. Last week got quite hectic for lots of people in IT dealing with multiple security issues.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@nschonni
chore: update messages on automated/official PRs
83c88bc
@nschonni
nschonni force-pushed the pr-body-updates branch from 78941b5 to 83c88bc Compare October 28, 2026 14:54
@nschonni
nschonni requested a review from MikeMcC399 October 28, 2026 14:54
MikeMcC399
MikeMcC399 approved these changes Oct 28, 2026
View reviewed changes

@MikeMcC399 MikeMcC399 left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll go along with this change as it puts a bit more information into users' hands. There will probably still be users who are impatient and post comments though.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@nschonni
nschonni merged commit 81d88a1 into nodejs:main Oct 28, 2026
1 check passed

Uh oh!

There was an error while loading. Please reload this page.

@github-actions

github-actions Bot commented Oct 28, 2026

Copy link
Copy Markdown

Created PR on the official-images repo (docker-library/official-images#22615). See https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what if you are wondering when it will be available on the Docker Hub.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot nodejs-github-bot mentioned this pull request Oct 28, 2026
Node: feat: Node.js v24.22.2 docker-library/official-images#22615
Merged
@nschonni
nschonni deleted the pr-body-updates branch October 28, 2026 16:15
@MikeMcC399 MikeMcC399 mentioned this pull request Oct 29, 2026
Consolidated official-images PRs retain only last version in title #2675
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@MikeMcC399 MikeMcC399 MikeMcC399 approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@nschonni @MikeMcC399
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.