fix: install uv in isolated account facts job - #325
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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
1 participant
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.
Change
Install the existing Runtime-pinned uv setup action in the isolated account-facts job before dependency preflight.
The reader revision, source qualification, broker scope, publishing credentials, and main Runtime remain unchanged.
Verification
57 account-facts tests and 92 Runtime workflow-security tests passed. actionlint, Ruff, and diff checks passed.
The failed real reader stopped before broker reads because uv was unavailable. Actual broker reads and homepage publishing still require separate acceptance after adoption.