cut-release

Automates versioned releases of a webOS app through CI with verification gates.

39|7|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/GLinnik21/plx-native --skill cut-release-glinnik21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cut-release
Source: https://github.com/GLinnik21/plx-native/tree/main/.agents/skills/cut-release
Command: npx skills add https://github.com/GLinnik21/plx-native --skill cut-release-glinnik21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing this webOS Plex client involves coupled steps — version bumps in four files, release notes, audits, CI publishing, and post-publish verification — where skipping any gate has historically shipped broken or misleading releases. This Skill encodes the full procedure and its hard-won rules so a release cannot silently bypass the checks. ## Core Features & Use Cases - CI-gated publishing: Dispatches release.yml via gh workflow run (including maintenance-line patch releases with line: and --ref), then confirms every gate job succeeded and assets were uploaded by github-actions[bot]. - Dual-document release artifacts: Guides writing the user-facing release note and the authored half of the release audit, with lint commands (ci/check-package.py --lint-note/--lint-audit) and generated audit previews. - Build integrity verification: Enforces FLAVOR=stable RELEASE=1 on every make invocation, hash-based proof of the shipped binary, and installing the real .ipk on a television the way a user would. - Use Case: When asked to "cut 0.6.2" or "ship a patch release", the Skill walks through bumping versions, writing both documents, dispatching the workflow from the right branch, verifying published assets, and updating the webosbrew listing. ## Quick Start Ask the assistant to cut and publish release version X.Y.Z of the app through the CI release workflow.

Frequently Asked Questions about cut-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a release with GitHub Actions workflow dispatch?

Run gh workflow run release.yml with -f version=X.Y.Z or -f bump=minor, then watch the run and confirm the build, redistributable assets, and publish jobs all report success. A bare git push --tags is not enough because the prepare job is gated on workflow_dispatch.

How do I cut a patch release from a maintenance branch?

Dispatch the workflow with both -f line=release/vX.Y and --ref release/vX.Y so GitHub validates inputs against the branch's copy of the workflow. Omitting --ref makes GitHub read the default branch and reject the line input as unexpected.

Why does my release build behave like a dev build?

Any make invocation without RELEASE=1 deletes release artifacts at parse time and produces a dev binary. Verify by comparing md5 hashes of pkg/plxnative against the binary installed on the television, and check the event log's first line for features=release.

Can I publish a release manually with gh release create?

No. Hand-published releases skip every CI gate, which is how v0.2.1 shipped a maintainer's home directory inside bundled FFmpeg libraries. Releases must go through the release.yml workflow so the check-package and verify-published gates run.

What must I do after a patch release lands on a maintenance line?

Cherry-pick or merge the real fixes back onto main, skipping version-bump and release-audit commits. Fixes left only on a release branch have caused re-investigated crashes because main was behind its own maintenance line.