Skip to content

chore(facade): target Web Host 1.0.69 - #260

Merged
AndrewKirkovski merged 1 commit into
masterfrom
chore/facade-web-host-1.0.69
Nov 12, 2026
Merged

AndrewKirkovski merged 1 commit into
masterfrom
chore/facade-web-host-1.0.69

Conversation

@AndrewKirkovski

Copy link
Copy Markdown
Contributor

Points the facade at Web Host 1.0.69 and records the hand-published 0.6.52 in the facade changelog.

  • The fe_facade_url default, the Makefile WEB_HOST_CDN, the README and the two tests that assert the URL now name webcomponents-1.0.69.
  • The vendored loading.js, import-map-bootstrap.js and their source maps are byte-identical to the 1.0.69 CDN files (apart from line endings), so they are unchanged.
  • Facade 0.6.52 is already on the Hub, published from this branch's head (pack 55.7 KB with the public_files embed, digest sha256:cf09d4e1245b77475431f87d6183a493dfb0c5ba8abe1ac88077f6c2c8d4fce8).
  • Release-As: 0.6.53 stops Release Please from proposing 0.6.52 again, which happened after the 0.6.50 hand publish (chore: release master #249, fixed by docs(facade): describe 0.6.51 and release it as 0.6.51 #250).

Verification:

  • src/facade/test: 116 of 116 tests pass, lint reports no issues.
  • app-template-raw consumer smoke in the iframe and fragment engines, first with this branch as a local replacement, then with the published 0.6.52 from the Hub. Every tab and route was opened, every request went to Web Host 1.0.69, every web component rendered content, and there were no console errors or failed requests. After wippy update wippy/facade, the consumer lock hash equals the publish digest.

Release-As: 0.6.53

Points the facade at Web Host 1.0.69 and records the hand-published 0.6.52 in the facade changelog.

Release-As: 0.6.53
@AndrewKirkovski
AndrewKirkovski merged commit 17ca470 into master Nov 12, 2026
49 of 50 checks passed
@AndrewKirkovski
AndrewKirkovski deleted the chore/facade-web-host-1.0.69 branch November 12, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant