Content Freshness

Freshness baselines and automated checks for Debian versions, lifecycle dates, LTS windows, AI tools, and release operations.

Content freshness marks pages whose facts change over time, preventing release dates, lifecycle windows, cloud image build IDs, Docker tags, package support, and deployment instructions from drifting.

Phase 44 Live

The release gate now includes:

corepack pnpm --dir web freshness:check
corepack pnpm --dir web facts:check

freshness:check reads the review baseline from web/lib/debian-facts.json and verifies that key pages still contain the current review date, official source links, and lifecycle dates that must stay synchronized. facts:check cross-checks the fact source against Debian's official Release files and all 8 localized pages.

Current Review Baseline

ItemCurrent valueSource
Current stableDebian 13 (Trixie)Debian Releases
Debian 13 release date2025-08-09Debian 13 release notes
Debian 13 regular security support ends2028-08-09Debian Releases
Debian 13 LTS ends2030-06-30Debian Releases
Debian 12 regular security support ends2026-07-12Debian Releases
Debian 12 LTS ends2028-06-30Debian Releases
Debian 11 LTS ended2026-08-31 (ended)Debian LTS
Debian 11 ELTS ends2031-06-30Extended LTS
Debian 12 ELTS ends2033-06-30Extended LTS
Debian 13 ELTS ends2035-06-30Extended LTS

Review date: 2026-09-26. Next mandatory review date: 2026-12-26.

Content That Must Be Checked

Content typeExample pagesRisk
Release lifecycleVersions & Lifecycle, EOLStale dates mislead upgrade planning
Latest newsDebian Latest NewsPoint releases, LTS transitions, and release plans change
AI tool installationAI ToolsThird-party installers, package names, and supported systems change
Deployment flowDeploymentCloudflare, Next.js, pnpm, and wrangler versions change
AI Skills distributionInstall & DistributionRegistry, tags, package format, and validation scripts change
Cloud & container imagesCloud Images & PlatformsCloud image build IDs and Docker tags change after point releases

Update Flow

  1. Check official sources first; do not copy lifecycle dates from summaries.
  2. Run corepack pnpm --dir web facts:sync to refresh web/lib/debian-facts.json from Debian's official Release files, cloud image metadata, and Docker Hub tags (the committed cache is kept when the network is unavailable).
  3. Update the version-sensitive pages (versions, eol, news, whats-new, download, bootable-media, server/cloud) with the new versions, dates, and image build IDs.
  4. Run corepack pnpm --dir web freshness:check.
  5. Run corepack pnpm --dir web facts:check to confirm the fact source and pages agree.
  6. Run the full corepack pnpm --dir web release:check.

When The Check Fails

Do not loosen the check immediately. First determine:

  • Whether the mandatory review date has arrived.
  • Whether Debian official sources changed lifecycle or release-note information.
  • Whether a page is missing official source links.
  • Whether only one of the Chinese or English pages was updated.

Next: Release Readiness.

On this page