Auto versioning

[Copilot]

Automates semver bumping and cache-busting on every PR merge to master via a GitHub Actions workflow + Node scripts.

Scripts

• scripts/bump-version.js — bumps VERSION in public/versioning.js, package.json, and package-lock.json; refreshes ?v= hashes in src/index.html (static imports) and across public/**/*.js (dynamic import() calls) for any files changed in the PR
• scripts/detect-bump-type.js — calls GitHub Models API (gpt-4o-mini) with the PR diff to determine patch / minor / major; falls back to patch on any error

Workflow (.github/workflows/bump-version.yml)

Triggers on pull_request closed+merged into master:

1. Checks out master branch explicitly (avoids detached PR merge ref so git push works)
2. Generates PR diff → AI-detects bump type → extracts base version from HEAD~1
3. Runs bump-version.js; skips version increment if the developer already bumped manually
4. Stages public/versioning.js, package.json, package-lock.json, src/index.html, and public/ (for dynamic-import hash changes), then commits and pushes via RELEASE_BOT_TOKEN (so the push triggers deploy.yml)

public/versioning.js

• Refactored inline <li> items into a latestPublicChanges array
• Fixed branch reference: main → master
• Added note that bumping is now automated

Type of change

• Bug fix
• New feature
• Refactoring / style
• Documentation update / chore
• Other (please describe)

Versioning

• Version is updated
• Changed files hash is updated

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR updates the post-merge version-bump workflow to ensure it checks out the base branch (so pushes work) and stages additional files that may be modified by cache-busting updates.

Changes:

• Check out the PR base branch ref (instead of the detached PR merge ref) to allow git push without extra arguments.
• Stage public/ so any public/**/*.js dynamic-import hash refreshes are included in the bump commit.

[Copilot]

Checking out the base branch ref is fine, but the workflow’s later use of HEAD~1 assumes the merge added exactly one commit to master (squash merge or a merge commit). If the repo ever uses “Rebase and merge” (multiple commits added), HEAD~1 will point to another PR commit and the generated diff / base-version extraction will be wrong. Consider computing the pre-merge base SHA from the PR payload (e.g., github.event.pull_request.base.sha) and diffing that against the post-merge tip, or otherwise handling rebase merges explicitly.

[Copilot]

git add public/ 2>/dev/null || true suppresses both stderr and failures from git add, which can mask real problems (e.g., a pathspec issue or permission error) and lead to silently skipping expected staged changes. Prefer an explicit existence check for public/ (or a more specific path/glob) and let git add fail if something is unexpectedly wrong.

Suggested change

	git add public/ 2>/dev/null || true
	if [ -d public ]; then
	git add public/
	fi