Publish Capture install asset - #4
Merged
Merged
Conversation
Add hardened HTTPS download for release-asset components (host allowlist, size cap, redirect boundary check). Fix stale CLI test that assumed the capture asset stayed unpublished.
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.
This PR completes the Capture install publication step for Scriptorium v0.2.0.
It updates the component catalog and installer so the standalone Capture profile downloads the published
capture-v1.0.0release asset from GitHub, verifies the pinned SHA-256 checksum, and installs the browser export bundle without cloning the full Provenance source tree.Validation already run locally:
PYTHONPATH=src python -B -m unittest discover -s tests -v-> 306 passed, 7 skippedscriptorium components --profile capture --jsonreports the Capture asset as published and checksum-pinnedscriptorium install capture --jsonpreview reports zero writes and network required only on--runThe previous public branch commit was amended to use the GitHub noreply author and committer email before this PR was opened.