Vendor rtichoke_viz v0.2.0 release - #374
Merged
Merged
Conversation
Contributor
|
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.
Summary
Replace the vendored
rtichoke_viz v0.1.0browser artifact with the exact immutablev0.2.0release artifact, without migrating production specs to v2.Provenance
v0.2.045dc109a6a0679d0f8f3f9452d8de9306a89b906rtichoke-viz-0.2.0.tar.gz3861277c01b3983f8b344a9ee0237c7d09fd0ba4c3d1e0cce489962e7b559d9fThe archive checksum was verified against both the published
.sha256sidecar and the value already independently verified inuriahf/rtichoke#178.Vendored files
rtichoke-viz.jsrtichoke-viz.cssCompatibility
Production/browser code remains on the existing v1 integration. Focused tests verify the v0.2.0 provenance, both canonical schema IDs, and representative v1 browser exports (
renderRoc,renderCalibration,RtichokeChartSpecSchema).No public API, statistical, or production-spec changes are included.