SWI-11363 ci(playground): publish playground.html as a rolling release asset - #20
Merged
Conversation
GitHub Pages is a dead end for this org — the org-wide Pages custom domain (dev.bandwidth.com) resolves to the S3/CloudFront dev-docs site, so no Pages deploy in the org actually serves. Instead, attach the built playground.html to a rolling 'playground-latest' release, refreshed on every push to main. Gives sellers one stable download link, no local build required.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
kshahbw
changed the title
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
laurelstreng
approved these changes
Jul 27, 2026
The playground-latest download link is used as a marketing asset on Bandwidth's website, so the tag and filename are a stable contract.
achandras
approved these changes
Jul 27, 2026
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
4 participants
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.
What
Replaces the GitHub Pages deploy (added in #19) with a rolling GitHub Release asset. On every push to
main, the workflow buildsdist/playground.htmland uploads it to aplayground-latestrelease with--clobber, so there's always one stable download link with the current build.Why
Pages doesn't work in this org: the org-wide Pages custom domain (
dev.bandwidth.com) resolves to the existing S3/CloudFront dev-docs site, so every repo's Pages URL redirects there and 404s. The deploy "succeeds" on GitHub's side but never serves. A release asset sidesteps DNS entirely and gives sellers a one-click download — no localnpm run playground:build.Result
Stable link once merged and run:
https://github.com/Bandwidth/bw-voice-adapter/releases/download/playground-latest/playground.html