← ClaudeAtlas

espos-firmware-releaseslisted

Publish firmware a browser-based flasher can actually download. Why GitHub release assets are unreachable from a web page, how to mirror them to a branch safely with force-with-lease, the GitHub Actions concurrency behaviour that silently drops a release (and the queue key that stops it), and the version-sort and no-checkout traps in release scripts.
signalk-espOS/skills · ★ 0 · Web & Frontend · score 72
Install: claude install-skill signalk-espOS/skills
# Publishing firmware a web flasher can fetch Verified against GitHub Actions, October 2026. ## Why release assets do not work in a browser **GitHub serves release downloads with no `Access-Control-Allow-Origin` header**, on the `302` and on the redirect target, so a web page cannot fetch them at all. A browser-based flasher (esptool-js, ESP Web Tools) pointed at a `github.com/.../releases/download/...` URL fails with a CORS error, not a 404, and no amount of client-side code fixes it. `raw.githubusercontent.com` **does** send the header and honours `Range` requests. So the working pattern is: keep the release as the archive, and mirror the same images to an orphan branch laid out as `<tag>/<asset>`. Server-side consumers keep using the release URL, which CORS does not affect. Two consequences worth planning for: * **Ordering.** If your catalogue/index derives a mirror URL by rewriting the release URL, it will publish links that 404 until the branch exists. Ship the workflow first, cut one release to populate the branch, *then* declare the mirror in the index. * **Mirror everything the index will advertise.** If the index emits both a "merged" and an "ota" web URL by rewriting, mirroring only the one your flasher reads leaves the other 404ing. Cheaper to mirror both than to make the index verify existence. ## Size the branch deliberately The branch is force-pushed as one commit with no history, so a clone is one snapshot rather than the sum of every release. I