release: staging to main, 2026-10-06

[bryanfawcett]

Release of staging to main. The branch is built from main with staging's exact tree (git diff origin/staging is empty).

What ships

• .github/workflows/staging-version.yml: tags every merge into staging as the next patch via the org reusable workflow (pinned by SHA). Triggers only on staging pushes and manual dispatch, so it does nothing on main.
• .DS_Store hygiene (.gitignore entry and/or removal of a committed .DS_Store).

No application code changes; no deploy surface.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GHjaH1Vt2dVLWU68iz8tFq

[bryanfawcett]

Merge gate record

Code review (code-review skill, on this PR's diff): reviewed against the pinned org reusable workflow reusable-staging-release.yml@924e5b4. Inputs, permissions (contents: write on the job, no secrets needed) and triggers match its documented usage. No blocking findings.

• Finding answered (low, not fixed here): workflow_dispatch is not restricted to staging, so a deliberate manual run started from main would tag a main commit as a beta patch. This is the org-wide caller template, already on main unchanged in auto-seo-manager, data-infra, nyuchi-docs, web-services and others; the right fix is one guard in the reusable workflow, not per-repo divergence. Raised upstream: Versioning policy: patch default, release:minor label, manual major .github#80 (comment). Manual-only, so non-blocking.

Verification (workflow/hygiene-only diff, no runtime surface): release tree equals staging (git diff origin/staging empty); actionlint clean and YAML parses on all workflows; required org lint + vite-plus checks green. On main the new workflow does not run automatically (push trigger is staging only).

🤖 Generated with Claude Code