Skip to content

Tell board owners a firmware exists that their board cannot - #298

Merged
engmung merged 1 commit into
mainfrom
dev
Aug 12, 2026
Merged

Tell board owners a firmware exists that their board cannot#298
engmung merged 1 commit into
mainfrom
dev

Conversation

@engmung

@engmung engmung commented Aug 12, 2026

Copy link
Copy Markdown
Owner

The console's "newer firmware is out" banner was added in v3.4.0 — so it only appears once you have already installed v3.4.0. Everyone on v3.1.0–v3.3.0 can update wirelessly today and has nothing anywhere telling them to. v3.0.0 and earlier need one USB flash, which /update already explains.

This site cannot close the gap by reading their board, either. I checked rather than assumed:

Mixed Content: The page at 'https://patternflow.work/update' was loaded over HTTPS,
but requested an insecure resource 'http://patternflow.local/api/status'.
This request has been blocked.

A control fetch to an unrelated http host was blocked identically, so this is the browser refusing http from https — not the board being offline. That asymmetry is the reason every device flow navigates to the board rather than reaching into it, and it rules out showing somebody their current version here.

So the notice goes where they already are: a thin strip above the community header. Quiet on purpose — it is news, not an error.

Dismissal is keyed to the version, not permanent. Nothing can know whether they went and updated, so asking once per release and then dropping it is the honest shape; a later release brings it back. Verified: visible → dismiss hides it → storing an older version brings it back.

🤖 Generated with Claude Code

The console's "newer firmware is out" banner was added in v3.4.0, so it
only appears once you have already installed v3.4.0. Everyone on v3.1.0
through v3.3.0 can update wirelessly today and has nothing anywhere
telling them to.

This site cannot fill the gap by reading their board either. A browser
refuses to let an https page fetch http at all, and a board is http -
verified rather than assumed:

  Mixed Content: The page at 'https://patternflow.work/update' was
  loaded over HTTPS, but requested an insecure resource
  'http://patternflow.local/api/status'. This request has been blocked.

That asymmetry is why every device flow navigates TO the board instead
of reaching into it, and it rules out showing somebody their current
version here.

So the only place left is a page they already visit, which is the
community. A thin strip above the header, quiet on purpose - it is news
rather than an error, and they came to look at patterns.

Dismissal is keyed to the version rather than permanent. Nothing can
know whether they went and updated, so asking once per release and then
dropping it is the honest shape; a later release brings it back.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pattern-flow_origin Building Building Preview Aug 12, 2026 6:37am
pattern-flow-open Ready Ready Preview Aug 12, 2026 6:37am

@engmung
engmung merged commit 892fd10 into main Aug 12, 2026
3 checks passed
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