Repository navigation
docs(fern): sync announcement configuration - #3436
Merged
Merged
Conversation
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
pimlock
requested review from
a team,
derekwaynecarr,
mrunalp and
sjenning
as code owners
September 18, 2026 00:03
|
🌿 Preview your docs: https://nvidia-preview-pr-3436.docs.buildwithfern.com/openshell |
drew
previously approved these changes
Sep 18, 2026
10 of 11 tasks
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
drew
previously approved these changes
Sep 18, 2026
drew
enabled auto-merge
September 18, 2026 01:11
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 18, 2026
Signed-off-by: Piotr Mlocek <pmlocek@nvidia.com>
drew
approved these changes
Sep 18, 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.
Summary
Teach the generated
docs-websitebranch to synchronize global and version-level Fern announcements without allowing one release channel to overwrite another. Treat the documentation inmainas thedevversion instead oflatest.Related Issue
No issue required: this is a localized documentation notice and publishing synchronization fix.
Changes
latesttodev, mark it beta, and use a channel-neutral source logo linklatestroutelatestand Release Tag cannot changedevdevrefreshes, including removing stale generated announcements when source configuration removes themlatestsynchronization from a v0.0.116 maintenance branch to add the final-alpha and migration notice to the already-published releaseTesting
mise run pre-commitpassesmise run test:docs-websitepasses, 26 testsmise run docspasses with 0 errors and 3 existing warningsChecklist
This PR does not publish production documentation. After merge, Release Dev can synchronize a development announcement only to
dev. Updating the already-published v0.0.116latestannouncement remains a separate, explicitly dispatched synchronization and publish operation.