Repository navigation
Handle cold Windows runner startup and verify PyPI artifacts - #2
Merged
Merged
Conversation
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.
A hosted Windows Python 3.12 job exceeded the regression harness's 10-second PowerShell startup allowance. Increase that harness allowance to 30 seconds while preserving every service-state assertion; runtime behavior is unchanged.
The publishing job now downloads the existing GitHub wheel/sdist and verifies GitHub's SHA-256 digests before upload, so PyPI receives the exact release files already tested. Publication remains manually dispatched and has not been started.
Validation: the targeted service-helper tests passed locally; both public release artifacts downloaded and verified successfully. The public wheel installed into a fresh venv, fetched its runtime, and received a real camera frame.