release

name	release
description	Release staged changes in Virgulas: run cache-busting scripts, branch, commit with Conventional Commits, push, and open a PR. Use when the user asks to create a release, ship changes, or publish staged work.
argument-hint	optional: describe the changes to include in the PR description

Virgulas Release Workflow

When to Use

• User asks to "create a release", "ship", "publish", or "open a PR" for staged changes.

Decision: which scripts to run

Before branching, determine what changed:

Changed files	Script to run
source/vendor/	npm run vendor:sync then npm run sw:bump
source/css/, source/js/, source/index.html, source/fonts/, source/media/	npm run sw:bump
Nothing in the above groups	No script needed

Run npm run sw:bump whenever any app or vendor file changes. It is idempotent and safe to run even when nothing changed — it will report "nothing bumped".

Procedure

1. Inspect staged changes

git diff --staged

Understand what changed to write the commit message and decide which scripts to run.

2. Run cache-busting (and vendor sync if needed)

If vendor files changed: