skills.rest
MarcelMichau
MarcelMichauCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bump-version

Bump the NuGet package version in DotNetStarterProjectTemplate.Package.csproj and README.md.

1|Updated Feb 4, 2025
Search Tags:#release#dotnet#semver#nuget#package#bump#version
One-click install
npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill bump-version-marcelmichau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/MarcelMichau/dotnet-starter-project-template/tree/main/.agents/skills/bump-version
Command: npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill bump-version-marcelmichau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bumps the template package version in two places: the PackageVersion in DotNetStarterProjectTemplate.Package.csproj and the version reference in README.md installation command.

Core Features & Use Cases

  • Synchronizes version numbers between the NuGet package and its installation command.
  • Supports exact version setting or semantic bumps (patch, minor, major).
  • Provides a repeatable, auditable workflow with a clear change report.

Quick Start

Specifies a target version or a bump type (patch, minor, or major) and the skill will update both DotNetStarterProjectTemplate.Package.csproj (PackageVersion) and README.md installation command.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I bump the NuGet package version in a .NET project template?▼

This Skill bumps the .NET template package version by updating DotNetStarterProjectTemplate.Package.csproj and README.md. It validates the current version, computes the target semantic version, applies updates to both files, and reports changes for a synchronized release.

What's the best way to synchronize a NuGet package version with its installation command?▼

The best way to synchronize package versions is by applying semantic versioning rules to update both the csproj and README simultaneously. This ensures the NuGet installation command always references the correct package version.

Can I set an exact version number instead of using a semantic version bump?▼

Yes, you can specify an exact version number instead of a patch, minor, or major bump. The tool validates the current version, applies your exact target to the csproj and README, and generates a report of the changes made.

How do semantic versioning rules apply when bumping a .NET template package?▼

Semantic versioning applies by calculating the next version based on your bump type: patch increments the third number, minor the second, and major the first. The tool computes this target and updates the csproj and README files.

What files need to be updated when releasing a new .NET template package version?▼

Updating a .NET template package version requires modifying DotNetStarterProjectTemplate.Package.csproj for the PackageVersion and README.md for the installation command. Synchronizing both files ensures the release is auditable and installation commands remain valid.

Related Skills

Explore More Software Engineering Skills→
publishpresspublishpress
9

update-plugin-version

Automate PublishPress Future version updates across post-expirator.php and readme.txt.

Official
Intermediate
webmaxruwebmaxru

nuget-manager

Manages NuGet package versions in .csproj or Directory.Packages.props files.

Community
Intermediate
William189189William189189

deployment-git

Coordinate Kailash Python SDK releases, PyPI publishing, and GitHub Actions pipelines.

Community
Advanced
Was85Was85

nuget-manager

Manage NuGet packages in .NET projects using the dotnet CLI.

Community
Intermediate