4gray
2ac0de752f
* docs(skills): design implementation synchronization * docs(skills): plan implementation synchronization * fix(release): filter internal notes from public body * docs(release): synchronize release workflow guidance * fix(stalker): normalize catalog series flags * fix(stalker): preserve progress with scoped episode IDs * fix(playback): expose strict position persistence * docs(stalker): record series position compatibility * test(skills): validate repository skill contracts * fix(database): keep SQL trace values private * docs(skills): refresh Nx and SQLite ownership * docs(skills): align provider and UI guidance * docs(skills): tighten validated guidance * docs(release): require exact release pushes * style(electron): remove trailing blank line * fix(ci): classify repository skills coverage
2.7 KiB
name, description
| name | description |
|---|---|
| release-cut | Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets. |
Release Cut
The tag workflow authors the public GitHub body with
node tools/release/extract-changelog-section.mjs --public "${VERSION}".
Keep the full changelog, including internal notes, committed before tagging.
Preflight
Work from clean, current master with the intended remote named explicitly.
Confirm package.json contains bare semver, the exact v<version> tag does not
exist locally or remotely, CI is green, and all notes validate.
pnpm run release:notes:validate
pnpm run i18n:check
Generate
- Set
package.json.version. - Run
pnpm run release:notes:changelog. - Minor release: run
pnpm run release:notes:blogand finish every editorial field. Patch release: edit the existingvX-Ypost; do not scaffold or force-overwrite it. - Capture required manifest screenshots only against mock servers:
pnpm nx run electron-backend:build-e2e, thenpnpm run release:screenshots. - Consume notes only after reviewing all generated output:
node tools/release/build-release-notes.mjs --consume.
The consume command is the destructive boundary: it deletes the direct note
files. Stage only release-owned files, including exact website post/assets and
git add -A -- .changes, then commit and create the exact tag.
git commit -m "chore(release): v0.24.0"
git tag v0.24.0
Push and External Effects
Push the named remote's master branch first, then push only the exact
v<version> tag as a second command. Never use broad git push --tags.
For remote upstream and version v0.25.1, run exactly:
git push upstream master
git push upstream v0.25.1
Master and v* pushes can publish Docker images. The tag build creates a draft
GitHub release. Verify authored text plus generated commits and all required
macOS, Windows, DEB, RPM, Pacman (.pacman/.pkg.tar.*), AppImage, Snap,
Flatpak, updater metadata, blockmaps, and
linux-frame-copy-runtime-sources.tar.xz.
After verification, manually publish the GitHub release. That publication
automatically verifies its Snap assets and uploads them to edge.
Installed-Snap smoke and candidate/stable promotion remain manual. Keep the
blog draft during artifact verification; publish it in a follow-up commit and
verify the website deployment.
Failure Safety
Missing CHANGELOG section: regenerate, commit, delete the bad tag locally and remotely only after resolving its exact target, then retag. Never publish a draft until the source archive and Snap contract pass.
The .codex and .claude copies of this skill must remain byte-identical.