skills.rest
technicalpickles
technicalpicklesCOMMUNITY
Explore all skills by this author →
Website𝕏@techpicklesGitHub

release

Automate version bumps, pre-release checks, and CI-driven releases for the envsense project.

5|1|Updated Aug 22, 2025
Search Tags:#workflow#versioning#release#cargo#ci#cosign
One-click install
npx skills add https://github.com/technicalpickles/envsense --skill release-technicalpickles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/technicalpickles/envsense/tree/main/.claude/skills/release
Command: npx skills add https://github.com/technicalpickles/envsense --skill release-technicalpickles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release workflow guides and automates the envsense project's release process, consolidating version bumps, pre-release checks, CI/CD coordination, and multi-platform artifact management.

Core Features & Use Cases

  • Version bumping in Cargo.toml on main
  • Pre-release verification: tests, formatting, linting, baselines
  • Multi-platform builds: Linux x64, Linux ARM64, macOS universal
  • Cryptographic signing with cosign
  • Release verification and troubleshooting
  • CI/CD monitoring and PR-based release workflow

Quick Start

Initiate a release by updating Cargo.toml to a new version and opening a PR to main, then monitor CI/CD progress.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust Cargo release versioning and publishing across Linux and macOS?▼

Automate Rust Cargo release versioning by bumping versions in Cargo.toml and opening a PR to main, which triggers CI to validate tests, linting, and multi-platform builds for Linux and macOS targets.

What pre-release checks are needed before publishing a Rust project with CI?▼

Required pre-release checks for publishing a Rust project include verifying formatting, running tests, checking linting, and establishing baselines to ensure code stability before triggering CI-driven release workflows.

How does cosign signing work for CI release artifacts?▼

Cosign signing for CI release artifacts generates cryptographic signatures for built binaries, ensuring artifact integrity and verifiable provenance across Linux and macOS platforms during the publishing process.

Can I trigger a release workflow by updating Cargo.toml?▼

Yes, trigger the release workflow by updating the version number in Cargo.toml on main and opening a PR, which synchronizes version updates with CI workflows to coordinate builds and publishing.

What is the best way to manage multi-platform builds for Rust projects?▼

Manage multi-platform Rust builds by configuring CI workflows to compile Linux x64, Linux ARM64, and macOS universal targets, ensuring consistent artifacts are generated and cryptographically signed.

Why are my CI release workflows failing after a Cargo version bump?▼

CI release workflows may fail after a Cargo version bump if pre-release validation detects formatting errors, linting issues, or failing tests, requiring troubleshooting to resolve build inconsistencies.

Related Skills

Explore More Software Engineering Skills→
Happyverse-TeamHappyverse-Team

release-bump

Bump ralph-orchestrator versions in Cargo.toml files and trigger the release workflow.

Official
Advanced
haomingzhaomingz
12

glab-attestation

Verify software artifact attestations using glab and cosign in GitLab CI pipelines.

Community
Intermediate
matteocervellimatteocervelli
25

rust-quality-checker

Run rustfmt, clippy, cargo check, test, and audit for Rust quality gates.

Community
Advanced
Minara-AIMinara-AI
28

publish

Automate versioning, tagging, and release workflows for Rust binaries and VSCode extensions.

Official
Advanced