feat: update demo (with latest release) in release script

Author: grega

README.md

@@ -134,8 +134,9 @@ The script:
 2. runs the tests and build,
 3. bumps the version (updating `package.json` / `package-lock.json`), commits, and tags `vX.Y.Z`,
 4. publishes to npm (prompting for your 2FA OTP if enabled),
-5. pushes the commit and tag, and
-6. creates a GitHub Release with notes generated from the commits/PRs since the previous tag.
+5. points the demo at the new release (bumps `docs/` to the just-published version) and commits it,
+6. pushes the commits and tag, and
+7. creates a GitHub Release with notes generated from the commits/PRs since the previous tag.
 
 If `npm publish` fails, nothing is pushed — the script prints how to undo the local
 bump and retry.

scripts/release.sh

@@ -77,6 +77,21 @@ if ! npm publish; then
   exit 1
 fi
 
+# ── Point the demo at the just-published version ────────────────────────────
+# The demo's "vendored release" build (served on GitHub Pages) is regenerated from the published npm package pinned in docs/
+newversion="${newtag#v}"
+pkg="@raspberrypifoundation/python-friendly-error-messages"
+echo "Pointing the demo at $newtag…"
+if ( cd "$ROOT/docs" && npm pkg set "dependencies.$pkg=^$newversion" && npm install >/dev/null 2>&1 ); then
+  git add docs/package.json docs/package-lock.json
+  git commit -m "chore: point demo at $newtag" >/dev/null
+else
+  echo "Warning: couldn't update the demo dependency — the new version may not have" >&2
+  echo "propagated to npm yet. Once it has, run:" >&2
+  echo "  (cd docs && npm install $pkg@^$newversion) && git commit -am 'chore: point demo at $newtag' && git push" >&2
+  git checkout -- docs/package.json docs/package-lock.json 2>/dev/null || true
+fi
+
 # ── Push + GitHub Release ───────────────────────────────────────────────────
 git push --follow-tags origin main