docs: Add note about the bot opening PRs

[nschonni]

Description

Makes a note about how the Bot will open PRs, but we do appreciate PRs when new major versions are released.

Motivation and Context

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.

[nschonni]

The link failure seems unrelated, and appears to still be rendering on the README

[bmuenzenmeyer]

@nschonni - brian from the website team here, I have had a TODO to document this process for a while. If I draft it up will you take a look? This seems like a great thing to make more clear, especially when security create urgency

WIP below

• every 15 minutes, the workflow within nodejs/docker-node checks for new versions of Node.js published to the website domain
• A pull request is opened either by nodejs-github-bot as a result of this automation or in some cases manually created
• Another automation detects the merger of these pull requests and submits new ones to docker-library/official-images, which builds and publishes images to docker hub

[nschonni]

Sure, feel free to suggest or push changes to this branch. This was just a quick idea so people wouldn't open PRs that we wouldn't land, but it could use finesse.

[bmuenzenmeyer]

@nschonni sorry for the double ping - I was editing as I worked to understand it myself. please take a look at my initial comment 😄

and thanks!

[nschonni]

That's probably useful info that could be either in this doc or the README. I think it probably needs to be clear in a few places. I think some of the mermaid diagrams have been used in the other repos too

[techgaun]

ok awesome thank you. Waiting for this.

[nschonni]

@nschonni - brian from the website team here, I have had a TODO to document this process for a while. If I draft it up will you take a look? This seems like a great thing to make more clear, especially when security create urgency

WIP below

• every 15 minutes, the workflow within nodejs/docker-node checks for new versions of Node.js published to the website domain
• A pull request is opened either by nodejs-github-bot as a result of this automation or in some cases manually created
• Another automation detects the merger of these pull requests and submits new ones to docker-library/official-images, which builds and publishes images to docker hub

Might want something that points to the next steps on the docker side. The automation links to that after the PR lands https://github.com/nodejs/docker-node/blob/main/.github%2Fworkflows%2Fofficial-pr.yml#L66

[SimenB]

makes sense 👍

[MikeMcC399]

Since this PR was originally written, #2345 was merged to create the documentation section

Image Creation Automation

Also, the documentation section

Release Availability

describes how security and non-security updates are handled, and their relationship with musl build availability.

I've submitted a new PR #2510 which I believe better describes the current process. Please feel free to review!