Repository navigation
feat(ui)!: publish paired WASM and OpenUI assets - #128
Merged
Merged
Conversation
BREAKING CHANGE: UI publication requires a nonempty .openui document beside the WASM component. Upload both under one immutable prefix before updating the active package.
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.
Summary
Boundaries
No new public HTTP endpoints, CLI flags or protobuf fields. RuntimeUIPackageUpload changes are internal.
Verification
Readiness
Draft: this integration was verified against the local build of highcard-dev/druid-ui#19 (9443dcb), published only to local Verdaccio as 4.0.0-rc.1. GitHub still reports SDK PR #19 as OPEN, not merged.
Before merge, publish the SDK RC, regenerate consumer lockfiles against the actual public tarballs (the current RC integrity hashes come from local packing), and rerun clean-install CI. Local registry URLs have been removed from committed lockfiles. Coordinate the host, runtime, Scrolls and developer image rollout; this is a breaking UI-package format change. No production deployment or public npm release was performed.
Coordinated PRs