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 — docs: document Debian lifecycle transitions by MikeMcC399 · Pull Request #2609 · nodejs/docker-node

Conversation

@MikeMcC399

@MikeMcC399 MikeMcC399 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Description

CONTRIBUTING > Version Updates is updated with information concerning Debian releases and lifecycle transitions.

Motivation and Context

Debian release lifecycle transitions require re-configuration action of node Docker image variants.

CONTRIBUTING > Version Updates does not yet include any related description.

Debian Releases > Release life cycle states:

Debian announces its new stable release on a regular basis. The Debian release life cycle encompasses five years: the first three years of full support followed by two years of Long Term Support (LTS).

  • Release
  • End of Life (EOL) after 3 years
  • End of LTS after another 2 years, 5 years in total

When Debian transitions from EOL to LTS, the LTS support team defines and publishes LTS support architectures that may be only a subset of the architectures supported during the original release phase.

Testing Details

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
@MikeMcC399 MikeMcC399 added docs build process labels Aug 20, 2026
@MikeMcC399 MikeMcC399 self-assigned this Aug 20, 2026
@MikeMcC399
docs: document Debian lifecycle transitions
b1fec91
Signed-off-by: Mike McCready <[email protected]>
@MikeMcC399
MikeMcC399 force-pushed the debian-lifecycle-transitions branch from 69c5050 to b1fec91 Compare August 20, 2026 09:24
@MikeMcC399

MikeMcC399 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

See #2610 for unrelated fix to markdown-link-check failure.

All reactions

Sorry, something went wrong.

Uh oh!

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

@MikeMcC399
MikeMcC399 marked this pull request as ready for review August 20, 2026 09:54
nschonni
nschonni approved these changes Aug 23, 2026
View reviewed changes
@MikeMcC399
Merge branch 'main' into debian-lifecycle-transitions
bd6b8d3
@MikeMcC399
MikeMcC399 merged commit 795ea2f into nodejs:main Aug 23, 2026
3 checks passed

Uh oh!

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

@MikeMcC399
MikeMcC399 deleted the debian-lifecycle-transitions branch August 23, 2026 15:14
@MikeMcC399 MikeMcC399 mentioned this pull request Aug 24, 2026
Add OS maintenance strategy to documentation #2397
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nschonni nschonni nschonni approved these changes

Uh oh!

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

Assignees

@MikeMcC399 MikeMcC399

Labels

build process docs

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

@MikeMcC399 @nschonni
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.