chore: add build number and release scripts

2026-05-12 20:52:35 -05:00
parent e7b74c827a
commit 7b1b5d0f6c
3 changed files with 23 additions and 0 deletions
@@ -22,6 +22,22 @@ npm run dev       # local dev server
 npm run build     # type-check + production build
 ```
 ## Releases
 The footer build number comes from Woodpecker's pipeline number and increments on each CI build.
 The package version is an intentional release label.
 Use one of these from a clean worktree when you are ready to cut a release:
 ```sh
 npm run release:patch  # fixes, typo corrections, small polish
 npm run release:minor  # meaningful playable additions or mechanics
 npm run release:major  # disruptive changes after 1.0.0
 git push --follow-tags
 ```
 Each release script updates `package.json` and `package-lock.json`, creates a release commit, and tags it.
 ## Layout
 - `src/engine/` — parser, dispatcher, encounter logic
@@ -11,6 +11,9 @@
    "build": "astro check && astro build",
    "preview": "astro preview",
    "astro": "astro",
    "release:patch": "npm version patch -m \"chore(release): %s\"",
    "release:minor": "npm version minor -m \"chore(release): %s\"",
    "release:major": "npm version major -m \"chore(release): %s\"",
    "test": "vitest run",
    "test:watch": "vitest"
  },
@@ -1,5 +1,7 @@
 ---
 import '../ui/crt.css'
 const buildNumber = process.env.CI_PIPELINE_NUMBER ?? 'local'
 ---
 <html lang="en">
@@ -80,6 +82,8 @@ import '../ui/crt.css'
        <span aria-hidden="true">|</span>
        <a href="https://half.st/ejlewis/halfstreet/src/branch/main/LICENSE">GNU 3.0</a>
        <span aria-hidden="true">|</span>
        <span>Build #{buildNumber}</span>
        <span aria-hidden="true">|</span>
        <a href="https://half.st/ejlewis/halfstreet">Source Code</a>
      </footer>
    </div>