Pin the install guide to v0.5.0 - #492
Merged
Merged
Conversation
The Install guide's Configuration manifest still asked for v0.3.1, so anyone following it installed a package two releases behind. The equivalent pin was bumped for v0.4, but that file was replaced by the Install guide shortly after and carried the old value across, where nothing caught it. Pinning ahead of the tag is deliberate: release-0.5 is what the 0.5 docs serve, so the pin has to name v0.5.0 before the branch is cut. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Dennis Ramdass <dennis@upbound.io>
|
Docs preview: https://modelplane-docs-pr-492.vercel.app (ready once the site's Content workflow finishes) |
haarchri
approved these changes
Oct 2, 2026
|
Successfully created backport PR for |
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.
Description of your changes
docs/manifests/install/configuration.yamlstill pinnedv0.3.1, so anyone following the Install guide installed a package two releases behind. It's rendered into the guide atdocs/content/install/_index.md:75.The equivalent pin was bumped for v0.4 in #447, but that file (
docs/manifests/getting-started/configuration.yaml) was replaced by the Install guide in ff7b845, which carried the oldv0.3.1value across. Nothing checks it, so it went unnoticed.Pinning ahead of the tag is deliberate and matches what #447 did:
release-0.5is what the 0.5 docs serve, so this has to namev0.5.0before that branch is cut.Worth a follow-up to make the release process catch this rather than relying on someone remembering — the pin is the one thing in the repo that has to change at release time and has no test.
I have:
nix flake check(or./nix.sh flake check) and made sure it passes.Added or updated tests covering any composition function changes.No composition function changes; this is a one-line docs pin.git commit -s.🤖 Generated with Claude Code