0.0.52 bump - #99
Merged
Merged
Conversation
…oordinator The README told readers managed mode "expects the declaration to provide equivalents" for the missing Wippy chrome, which understates it: below Web Host 1.0.50 a child app's `host.openArtifact()` / `startChat()` / `openSession()` / `navigate()` calls fail *silently* in managed mode, and nothing binds the host URL to a panel — so deep links, the browser Back button and nav-sidebar clicks change the address bar and render nothing. Adds the version floor, the `@HOST/compat-coordinator` declaration that closes it, and a pointer to `managed-layout.md`. Claude-Session: https://claude.ai/code/session_01XpA4dkMx2PhiW63aCeidcN
Updates the four files that carry the ref: the `fe_facade_url` default in `_index.yaml`, `WEB_HOST_CDN` in the Makefile, the README's requirements table and sample config output, and the expected URL in `config_handler_test.lua`. 1.0.50 is the version where managed mode stops failing silently — see the managed-mode note added to the README earlier on this branch. Still owed before publish: `make sync` to re-vendor `public/@wippy-fe/` from the new CDN, which can only run once the host bundle is deployed. Claude-Session: https://claude.ai/code/session_01XpA4dkMx2PhiW63aCeidcN
Bumps the CDN ref in all four places that carry it: the `fe_facade_url` requirement default, the Makefile's `WEB_HOST_CDN`, the README examples, and the config-handler test fixture. `make sync` is NOT run here — 1.0.51 is not on the CDN yet (403), so re-vendoring `public/@wippy-fe/loading.js` has to follow the host deploy. Run it before publishing the facade, and check the pack is ~25-45 KB: a ~2-3 KB pack means the `public_files` embed was dropped. Claude-Session: https://claude.ai/code/session_01XpA4dkMx2PhiW63aCeidcN
Bumps the CDN ref everywhere it appears, and fixes two assertions that every previous bump missed because they live outside the four files the release checklist names: - `test/config_dependency_test.lua:12` still expected the `fe_facade_url` default to be `webcomponents-1.0.49` — stale since the 1.0.50 bump. - `config_handler_test.lua:269` still expected it to be `https://front.wippy.ai`, the deprecated domain. Both read the real registry default out of `_index.yaml`, so both have been asserting a value the module does not produce. Found by sweeping every URL in the module rather than the known file list; worth adding that sweep to the checklist. The remaining `front.wippy.ai` occurrences are test INPUTS (a configured value whose derived `iframe_url` / origin the test then checks), not defaults, so they stay as fixtures. `make sync` re-vendored `public/@wippy-fe/loading.js` from the 1.0.52 CDN; the bytes are unchanged from 1.0.51, so the embed is byte-identical. Claude-Session: https://claude.ai/code/session_01XpA4dkMx2PhiW63aCeidcN
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.
0.0.52 bump