passlane-release

Automates project releases by updating changelog, tagging git commits for CI.

26|1|Updated May 2, 2022

Search Tags:#git #changelog #release #cargo #ci #version #tag

Ready to run

npx skills add https://github.com/anssip/passlane --skill passlane-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: passlane-release
Source: https://github.com/anssip/passlane/tree/main/.claude/skills/passlane-release
Command: npx skills add https://github.com/anssip/passlane --skill passlane-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Passlane release automation streamlines the process of bumping versions, updating the changelog, and tagging releases so CI can publish artifacts.

Core Features & Use Cases

Automatically update CHANGELOG.md and Cargo.toml when preparing a new release.
Commit release changes and create a git tag in the form vX.Y.Z to trigger CI-based releases.
Manage end-to-end release workflows for cutting, publishing, and tagging new Passlane versions across repositories.

Quick Start

Run the release command after confirming the next version to update the changelog, cargo manifest, and tag the release for CI.

Frequently Asked Questions about passlane-release

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

FAQPage Schema

How do I automate updating CHANGELOG.md and Cargo.toml for a new release tag?▼

To automate a release tag, this Skill updates CHANGELOG.md and Cargo.toml with the new semantic version, commits the changes, and creates a git tag formatted vX.Y.Z to trigger CI workflows.

What is the best way to cut a semantic version release across multiple repositories using git and cargo?▼

Cutting a semantic version release across repositories requires updating the cargo manifest and changelog consistently, then tagging the version in git history to ensure CI publishes artifacts uniformly.

How do I trigger CI releases by creating a git tag for a Rust project?▼

You can trigger CI releases by creating a git tag in the format vX.Y.Z after committing version bumps to Cargo.toml and CHANGELOG.md, which signals the continuous integration pipeline to publish artifacts.

Do I need the GitHub CLI installed to tag a release and update the changelog?▼

Yes, interacting with GitHub release workflows and manipulating git history requires tools such as git, cargo, and gh to ensure the release tag triggers CI successfully and manifests are updated.

Why does my release workflow require updating both the changelog and cargo manifest before tagging?▼

Updating both the changelog and cargo manifest before tagging ensures consistency across project files, so the semantic version accurately reflects documentation and dependencies when CI publishes the release.