swpm-release

Bump SWPM versions in package.json and update CHANGELOG.md from commits.

125|5|Updated May 13, 2022
One-click install
npx skills add https://github.com/deinsoftware/swpm --skill swpm-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swpm-release
Source: https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-release
Command: npx skills add https://github.com/deinsoftware/swpm --skill swpm-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automate SWPM release preparation by handling version bumps, changelog maintenance, and release tagging to reduce manual errors during software releases.

Core Features & Use Cases

  • Reads current version from package.json and suggests a new version based on commits since the main branch.
  • Updates package.json (and package-lock.json when present) and migrates [Unreleased] entries into a new version section in CHANGELOG.md with the current date.
  • Generates release instructions and a ready-to-copy tag snippet for publishing.

Quick Start

Execute the release script to start the version bump and changelog update workflow.

Frequently Asked Questions about swpm-release

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

FAQPage Schema
How do I automate a Node.js package release and update the CHANGELOG?

Automate Node.js package release by running a script that bumps the version in package.json, updates package-lock.json, and migrates Unreleased CHANGELOG entries to a new SemVer section with the current date.

How does commit analysis determine SemVer version bumps for a Git repository?

SemVer version bumps are determined by analyzing Git commits against the main or master branch, suggesting a major, minor, or patch bump based on the changes found before updating package.json.

Do I need an Unreleased section in my CHANGELOG to automate release notes?

Yes, you need a CHANGELOG with an Unreleased section. The automation migrates these entries into a new version section formatted with the current date, adhering to Keep a Changelog standards.

What's the best way to prepare a Node.js project for Git tagging and publishing?

Prepare for Git tagging by automating version bumps and CHANGELOG updates, which outputs ready-to-copy tag snippets and release instructions to guide the publishing workflow.

Can I use this release automation without a package-lock.json file?

Yes, the automation updates package-lock.json only when present, but it requires package.json, a Git repository, Node.js, and a CHANGELOG file with an Unreleased section to function correctly.

Why does my automated changelog update follow Keep a Changelog conventions?

The automated changelog update follows Keep a Changelog conventions to ensure standardized documentation, moving Unreleased entries into a clearly dated new version section alongside the package version bump.