skills.rest
coreos
coreosOFFICIAL
Explore all skills by this author →
WebsiteGitHub

publish-release

Guide post-merge Afterburn releases with branch creation, tagging, and vendor archives.

231|130|Updated Jul 22, 2015
Search Tags:#automation#github#release#cargo#vendor#crates.io#gpg
One-click install
npx skills add https://github.com/coreos/afterburn --skill publish-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-release
Source: https://github.com/coreos/afterburn/tree/main/.opencode/skills/publish-release
Command: npx skills add https://github.com/coreos/afterburn --skill publish-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It guides and automates the multi-step post-merge release workflow for Afterburn so maintainers can reliably create release branches, signed tags, vendor archives, and GitHub releases without missing verification or cleanup steps.

Core Features & Use Cases

  • Verifies that the pre-release PR was merged and that dependency update commits are present.
  • Performs clean build verification with vendored dependencies, runs tests, and prepares a vendor archive with SHA256 digests.
  • Guides the user through credential-gated steps such as running cargo release, pushing tags, and publishing to crates.io, and drafts the GitHub release notes from repository release notes.
  • Use case: a maintainer preparing a new Afterburn version can run the workflow to produce a release branch, open and merge the release PR, publish the crate, create a vendor tarball, and assemble the GitHub release body.

Quick Start

Run the publish-release workflow with the desired version, for example: /publish-release 5.11.0

Frequently Asked Questions about publish-release

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

FAQPage Schema
How do I automate a Rust crate release to crates.io with a vendor archive and GPG signed tags?▼

Automate a Rust crate release by guiding post-merge steps: creating release branches, generating GPG signed tags, publishing to crates.io, and assembling a vendor archive with SHA256 digests for GitHub releases.

What steps are required to publish a Rust crate with vendored dependencies and SHA256 digests?▼

Publishing a Rust crate with vendored dependencies requires verifying merged PRs, performing clean build verification, running tests, generating a vendor archive with SHA256 digests, and executing credential-gated crates.io publishing.

Do I need GPG signing and cargo release to publish a crate to crates.io using this workflow?▼

Yes, GPG signing and cargo release are required. The workflow performs automated verification, packaging, and cleanup while prompting the user for credential-gated actions such as GPG signing and crates.io publishing.

How does GitHub release preparation work when creating a vendor tarball for a Rust project?▼

GitHub release preparation drafts release notes from repository notes, creates a vendor tarball with SHA256 digests, and requires manual confirmation for pushing tags and publishing the crate to complete the release.

Why does my crate release workflow require manual intervention for crates.io publishing and tag pushing?▼

Crates.io publishing and tag pushing require manual intervention because they are credential-gated actions. The workflow automates verification, packaging, and cleanup but prompts the user to execute these sensitive steps.

Related Skills

Explore More Software Engineering Skills→
YanCheng-goYanCheng-go
3

release

Generate a changelog, bump the version, and open a release PR.

Community
Intermediate
baekenoughbaekenough
13

omcustom-release-notes

Generate markdown release notes from git history and closed issues.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-tag

Create, manage, and push Git tags for release workflows.

Community
Intermediate
dhntdhnt

tag-release

Create and push annotated Git tags for version-bump commits.

Official
Intermediate