fix(powercontext): use --frozen for Codex plugin uv commands - #1211
Merged
Conversation
222twotwotwo
pushed a commit
to 222twotwotwo/powercontext
that referenced
this pull request
Aug 23, 2026
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.
Which issue or RFC does this PR close?
Closes #1210.
Rationale for this change
The PowerContext Codex plugin runs project-local helper scripts with
uv run --locked.When a user's global uv configuration uses a custom package index while the bundled
uv.lockrecords PyPI, uv considers the lockfile outdated and exits. This breaks both theUserPromptSubmithook and theproject-contextskill.Using
--frozenallows the plugin to trust its bundled lockfile without checking or modifying it.What changes are included in this PR?
--lockedwith--frozenin theUserPromptSubmithook command.--lockedwith--frozenin theproject-contextskill command.Are there any user-facing changes?
Yes. The Codex plugin can now run when users configure a custom uv package index without requiring them to regenerate the plugin's lockfile.
There are no breaking changes.
How was this change tested?
--lockedwhile using the Tsinghua PyPI mirror.--frozen.hooks/hooks.jsonwithpython3 -m json.tool.git diff --check upstream/master...HEAD.AI usage statement
OpenAI Codex (GPT-5.6) was used to inspect the affected plugin paths, reproduce the uv index and lockfile behavior, and draft the change and PR description. The final diff and validation results were reviewed by the contributor.