docs(web): use active doc version for install manifest link - #1074
Open
mnencia wants to merge 5 commits into
Open
docs(web): use active doc version for install manifest link#1074mnencia wants to merge 5 commits into
mnencia wants to merge 5 commits into
Conversation
dosubot
Bot
added
size:M
mnencia
force-pushed
the
dev/docs-install-manifest-version
branch
from
August 25, 2026 12:21
807babf to
8a9aae1
Compare
mnencia
changed the title
dosubot
Bot
added
size:L
mnencia
force-pushed
the
dev/docs-install-manifest-version
branch
from
August 27, 2026 16:34
3763571 to
f9e59c5
Compare
The install snippet always linked to the manifest of the latest released version, regardless of which versioned docs page it was rendered on. Viewing the 0.13.0 installation page therefore pointed at the 0.14.0 manifest. Fall back to the latest released version only when there is no active version, or the active version is the unreleased "current" docs. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Docusaurus already exposes the latest released version via useLatestVersion (backed by GlobalVersion.isLast), making the manual filter and numeric-string sort redundant. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
The unversioned "current" docs describe unreleased functionality, so a tagged release manifest doesn't make sense there. Install from the manifest built off main instead. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Its 'latestReleased' branch had no remaining caller after the previous commit, and InstallationSnippet was calling useActiveVersion twice (once directly, once through the hook) to re-run the same check. Build the manifest URL straight from the active version and drop hooks/versions.ts entirely. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
The installation page said "the manifest for the latest release" everywhere, even on older versioned docs and on the unreleased Dev docs. Show the actual version instead (or "the latest development snapshot from the main branch" on Dev docs). The "Testing the latest development snapshot" section now explains, on Dev docs, that the command above already installs that snapshot, instead of duplicating it. Signed-off-by: Danish <danish.khan@enterprisedb.com>
mnencia
force-pushed
the
dev/docs-install-manifest-version
branch
2 times, most recently
from
August 28, 2026 09:15
6ef00ff to
d1c3639
Compare
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.
The install snippet always linked to the manifest of the latest released version, regardless of which versioned docs page it was rendered on. Viewing the 0.13.0 installation page therefore pointed at the 0.14.0 manifest.
Build the manifest URL from the active doc version directly: each versioned page links its own release tag, and the unreleased "current" docs link the manifest built off
maininstead of a (nonexistent) release tag.