website-builder 0.21 — the publish check tells access problems from network ones 🔑
As always: your favorite AI assistant takes you by the hand — just ask it, in your own
words, and it does the work.
What's new:
- 🔑 A permission problem is no longer treated as a bad connection. When GitHub refuses
a publish because of access — a changed security key, an expired login, or someone
removing your permission — 0.20 could read it as a wobbly connection and quietly try
again. It now says what it is, and stops, because trying again was never going to help. - 🔌 Better handling of an upload that dies half-way. More of the ways a connection can
fail mid-upload are now recognised, and told apart from problems that only look
similar — a rejected upload that's actually too large, for instance, is no longer
mistaken for a dropped one. - 🧭 Every failure message now tells you where you stand, not just what went wrong —
whether anything changed on your live site, and what's safe to run next. That's now a
written rule for the toolkit, so it stays true as it grows. - 🔁 Already have a site? Nothing changes on its own. Ask your assistant: "update my
site's publish script to website-builder 0.21" — it swaps two files in and runs the
built-in check, which tells you straight away if anything didn't land.
New here? How to start: download website-builder.zip below, unzip it, and paste the
starter prompt from the README
into your AI assistant — it takes you by the hand from there.
For the technically curious: the details are in PR #74.