Hide unreleased CDN changelog bundles on the current content source - #3857
Open
cotti wants to merge 1 commit into
Open
Hide unreleased CDN changelog bundles on the current content source#3857cotti wants to merge 1 commit into
cotti wants to merge 1 commit into
Conversation
cotti
force-pushed
the
feature/changelog-versions-visibility
branch
from
August 13, 2026 12:48
6937b43 to
fd6b529
Compare
Prestage products upload release bundles to S3 weeks before release day
(RFC B1, docs-eng-team#698). CDN-mode {changelog} rendering now checks a
bundle's target version against the product's versioning system: builds
publishing the 'current' content source (production) hide targets newer
than the current release, while 'next' (staging) keeps them visible for
pre-release review — the versions.yml bump on release day flips them
live automatically. BuildContext learns the assembler's content source;
isolated/local builds and versionless products are never filtered.
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
cotti
force-pushed
the
feature/changelog-versions-visibility
branch
from
August 13, 2026 12:48
fd6b529 to
4a68707
Compare
Mpdreamz
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why
Prestage products commit and upload release bundles to S3 weeks before release day, so the CDN holds bundles for versions that are not released yet. Without filtering, those staged bundles would render on production the moment they upload (RFC B1, docs-eng-team#698) — this is the gate that makes the whole Prestage path safe to roll out.
What
CDN-mode
{changelog}rendering now checks each bundle's target version against the product's versioning system inversions.yml:currentcontent source (production) hide bundles targeting versions newer than the current release, with a hint diagnostic.next(staging) keep them visible — pre-release review works as the RFC prescribes — and theversions.ymlbump on release day flips them live on production automatically.cloud-serverless) are never filtered.To make the decision possible at render time,
BuildContextnow carries the assembler'sContentSource(set from the publish environment; null for isolated builds). Directive docs gained an "Unreleased-version visibility" section.Stack: 4/5.