bifrost:release

What problem does it solve?

Bifrost's release process spans three distinct rungs (dev, pre-release, full release) with mandatory pre-checks, plugin manifest synchronization, contributor attribution, release notes drafting, and Kubernetes deployment steps, all of which are complex and error-prone to manage manually.

Core Features & Use Cases

• Three-rung release orchestration: Handles dev pushes (CI :dev image builds on main merge), pre-release candidate tagging (vX.Y.Z-rc.N tags with pre-release GitHub Releases), and full stable releases (vX.Y.Z tags with :latest images and final GitHub Releases).
• Automated pre-release guardrails: Runs unit tests, documentation freshness checks, plugin manifest version guards, external contributor attribution cross-checks, and CVE tracking to ensure releases meet OpenSSF Best Practices criteria.
• Use Case: A Bifrost maintainer merging a new feature to main can use this skill to automatically validate tests, push the dev image, and get clear instructions for K8s rollout, or cut a full production release with properly attributed release notes without missing any mandatory steps.

Quick Start

Invoke the bifrost-release skill to handle the full end-to-end stable release process for Bifrost after merging all changes to the main branch, including pre-release checks, release notes drafting, and version tag pushing.