release
Release
Automate the full release cycle: version bump → test → build → commit → push branch → open PR → merge → tag → GitHub Release.
Direct pushes to main are blocked by a branch ruleset. All releases go through a PR.
Preferred GitHub Actions flow
The default release path is now GitHub Actions-driven:
- Run the Prepare Release workflow (
.github/workflows/prepare-release.yml) - Review/approve the generated release PR
- Let GitHub auto-merge the PR after checks pass
- The Tag Release workflow (
.github/workflows/tag-release.yml) tags the merge commit - The Release workflow (
.github/workflows/release.yml) runs for that tag and publishes the artifacts
The manual flow below remains the fallback/operator path when you need to release outside GitHub Actions.
Version files
More from ekroon/tabctl
tabctl
Manage and analyze Edge tabs and groups with tabctl. Use GraphQL-first workflows via `tabctl query` for browser reads and mutations, and keep mutations explicit and reversible.
44git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
14