e45bff419d
Two issues in the pipeline: 1. cancel-in-progress: true could cancel a running deployment when a new push arrives. Deployments should never be interrupted mid-flight. Changed back to false. 2. The prod-release job bumps the version, commits, and tags — but never publishes the release version to npm. The dev-publish step publishes @dev, test-verify promotes to @next, but @latest was never updated. Users running 'npm install -g gsd-pi' would get stale versions. Added 'Build release' and 'Publish release to npm @latest' steps after the git tag push, with idempotent guard for already-published versions. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| FUNDING.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||