Repository navigation
Clarify uv frozen sync guidance - #4233
Merged
Merged
Conversation
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
matthewhelmke
approved these changes
Oct 16, 2026
matthewhelmke
left a comment
matthewhelmke
left a comment
Collaborator
There was a problem hiding this comment.
Very clear, thank you!
This branch was successfully 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
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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Update to Python overview, build configuration, and migration
What should this PR do?
State that
uv sync --frozencan still query configured indexes, clarify guidance around frozen syncsWhy are we making this change?
Requested in DOCS-240
What are the acceptance criteria?
Content should be accurate
How should this PR be tested?
Any documentation published to Chainguard Academy is reviewed carefully for accuracy. GUI procedures, API commands, and CLI code snippets in a draft are run and tested thoroughly — by both the author and the reviewer — to confirm they work exactly as written. This helps ensure that readers can follow along and get the same results. See the
edurepo's README.