Repository navigation
Docs: the landing version falls back to a fixed release, 0.5.2, not the latest - #76
Open
jonathan-taylor wants to merge 1 commit into
Open
jonathan-taylor wants to merge 1 commit into
jonathan-taylor wants to merge 1 commit into
Conversation
…he latest With no landing.txt on gh-pages (e.g. the branch remade), the site's root went to the latest release. It now goes to DEFAULT_LANDING, set in the workflow to 0.5.2 and bumped by hand, and landing.txt keeps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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 site's root redirects to the version in
landing.txton gh-pages. When that file was missing, for example after gh-pages was rebuilt from scratch, the workflow fell back to the latest release. After 0.7.0 that would quietly send readers to 0.7.0, but the root should stay on 0.5.2.The deploy job now has a fixed
DEFAULT_LANDING: '0.5.2', which is bumped by hand:-f landing=X.Y.Zstill sets the landing version, and is kept inlanding.txt.landing.txtis still kept. Today it holds0.5.2.landing.txt, the workflow usesDEFAULT_LANDINGand writes it tolanding.txt.I tested the deploy script against a mock gh-pages with
0.5.2/,0.6.0/,0.7.0/anddev/:landing.txtlanding.txtis written)landing.txt= 0.6.0-f landing=0.7.0The YAML parses. The header comment, the input's description and the changelog entry now describe the new fallback.
🤖 Generated with Claude Code