Repository navigation
Pin the docs to claude-sandbox 5.1.1, the first release whose pins work with --minimal - #113
Merged
Merged
Conversation
…rk with --minimal 5.0.0 rejects --minimal (exit 2), so docs that pinned 5.0.0 while advising --minimal gave a failing postCreate. Pin 5.1.1, which will be tagged right after this merges. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AJKFfYT7qdSfhkZGj6syCo
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 how-to pages pinned claude-sandbox 5.0.0 and, a few lines later, told readers to add
--minimal. 5.0.0'sinstalldoes not know that flag: its argument loop ends inunknown argument; exit 2, so aset -euo pipefailpostCreate that follows both pieces of advice fails on rebuild.This bumps every user-facing pin to 5.1.1, the release to be tagged right after this merges (it will carry this change and #106):
docs/how-to/sandbox-a-team-devcontainer.md: theuvx claude-sandbox==line in the postCreate example.docs/how-to/install-without-uv.md: the pipx and venvpip installpins, and thegit clone --branchtag.docs/how-to/upgrade.md: theuv tool install claude-sandbox==example.docs/reference/whats-installed.md: "The VS Code extension will install this way" becomes "installs this way"; the extension now installs with--minimal.Left as they are: the 5.0.0 beta examples in
upgrade.md(they show how to name a prerelease, and those betas exist), the "Upgrading from 4.x" history, and the ADRs.The pins point at a tag that does not exist until 5.1.1 is cut, so the published docs will name an uninstallable version until the release is out. Nothing in CI checks pins against PyPI or tags.
sphinx-build -b html -W --keep-going docspasses.🤖 Generated with Claude Code
https://claude.ai/code/session_01AJKFfYT7qdSfhkZGj6syCo
🤖 Generated with Claude Code
https://claude.ai/code/session_01AJKFfYT7qdSfhkZGj6syCo