skills.rest
deinsoftware
deinsoftwareOFFICIAL
Explore all skills by this author →
𝕏@deinsoftwareGitHub

swpm-semver

Calculate SemVer 2.0.0 version bumps for SWPM releases from package.json and CHANGELOG.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic Versioning 2.0.0 guidance for SWPM: defines when to bump major, minor, or patch and activates when the CHANGELOG.md is updated or the version in package.json changes.

Core Features & Use Cases

  • Enforces MAJOR, MINOR, and PATCH increment rules for SWPM releases.
  • Provides clear guidance on updating CHANGELOG.md per Keep a Changelog conventions.
  • Supports pre-release and build metadata patterns to track release qualification.

Quick Start

Check the current version in package.json, review the recent CHANGELOG.md entries, and apply the appropriate SemVer bump before releasing.

Frequently Asked Questions about swpm-semver

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

FAQPage Schema
How do I calculate the correct SemVer version bump for a package.json release?▼

To calculate a SemVer version bump, review recent CHANGELOG.md entries to determine if changes require a MAJOR, MINOR, or PATCH increment, then apply the correct version number to package.json before releasing.

What is the best way to format a CHANGELOG.md file for semantic versioning?▼

The best way to format a CHANGELOG.md for semantic versioning is applying Keep a Changelog conventions, ensuring entries clearly categorize changes to guide accurate MAJOR, MINOR, and PATCH release decisions.

When do I need to bump the major version instead of a minor or patch version?▼

You need to bump the major version when introducing incompatible API changes, bump minor for backward-compatible features, and bump patch for backward-compatible bug fixes, following SemVer 2.0.0 rules.

Does this enforce pre-release and build metadata patterns for version qualification?▼

Yes, it enforces pre-release and build metadata patterns to track release qualification, ensuring package.json versions align with SemVer 2.0.0 specifications and SWPM release policy guidelines.

Can I use this to check if my CHANGELOG.md aligns with my package.json version?▼

Yes, you can check alignment by verifying the version field in package.json matches the recent CHANGELOG.md entries, ensuring both follow the specified format and SWPM release policy before publishing.

Why does my SWPM release fail when my changelog and package versions are misaligned?▼

SWPM releases fail when misaligned because the versioning process requires the package.json version field and CHANGELOG.md entries to strictly follow the specified format and be aligned with SWPM release policy.

Related Skills

Explore More Software Engineering Skills→
jubscodesjubscodes
49

gspdev-changelog

Update CHANGELOG.md from git history following Keep a Changelog format.

Community
Intermediate
AEtherlight-aiAEtherlight-ai

publish

Automate ÆtherLight release publishing to npm and GitHub.

Official
Intermediate
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced