umb-update-server-dependencies-for-minor

Updates NuGet dependencies to latest minor and patch versions, then builds, tests, and opens a PR.

5.2k|2.9k|Updated Jun 10, 2013
One-click install
npx skills add https://github.com/umbraco/Umbraco-CMS --skill umb-update-server-dependencies-for-minor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umb-update-server-dependencies-for-minor
Source: https://github.com/umbraco/Umbraco-CMS/tree/main/.claude/skills/umb-update-server-dependencies-for-minor
Command: npx skills add https://github.com/umbraco/Umbraco-CMS --skill umb-update-server-dependencies-for-minor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Umbraco CMS server-side NuGet dependencies current across a release line is a repetitive, error-prone chore involving version discovery, template syncing, builds, tests, and PR creation. This Skill automates the entire routine while enforcing strict guardrails against major-version jumps and unwanted pre-release upgrades.

Core Features & Use Cases

  • Safe dependency discovery and upgrade: Runs dotnet-outdated with --version-lock Major and --pre-release Auto so only minor/patch bumps are applied and stable packages never move to pre-release.
  • Template project synchronization: Manually aligns templates/UmbracoExtension package versions with the root Directory.Packages.props, since those projects are outside the solution.
  • Build, test, and PR automation: Builds the solution in Release, runs the unit test suite, checks for vulnerable transitive packages, commits, and opens a PR with a generated change table.
  • Use Case: When preparing the 17.6 release, ask the Skill to update server dependencies; it bumps all outdated NuGet packages on a task branch, verifies the build and tests, and opens a PR against v17/dev.

Quick Start

Ask the assistant to update the server-side NuGet dependencies to their latest minor and patch versions for the current branch and open a PR.

Frequently Asked Questions about umb-update-server-dependencies-for-minor

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

FAQPage Schema
How do I update NuGet packages to latest minor versions only?

Run dotnet-outdated with `--version-lock Major` to restrict upgrades to the current major version line. Adding `--pre-release Auto` ensures stable packages never jump to pre-release while existing pre-release packages can still move to newer pre-releases.

How to update NuGet dependencies in Umbraco CMS for a release?

Check out the release line branch, run dotnet-outdated against umbraco.sln with major version locking, then manually sync the templates/UmbracoExtension project versions. Build in Release with `-p:UmbracoBuild=true`, run the unit tests, and open a PR against the line's dev branch.

Does dotnet-outdated update projects not included in the solution?

No, dotnet-outdated only processes projects referenced by the solution file. The templates/UmbracoExtension project is not part of umbraco.sln, so its package versions must be updated manually to match the root Directory.Packages.props.

Why does dotnet-outdated show a restore failure after upgrading?

The 'Failed to restore project after upgrading' message is a known quirk with the multi-level tests/Directory.Packages.props merge in this repository. The version writes still land correctly, so verify the changes with git diff rather than re-running the tool.

Can this process upgrade a package to a new major version?

No, major version upgrades are explicitly out of scope and blocked by the `--version-lock Major` flag. Packages with only major updates available, and packages marked HOLD or do-not-bump in Directory.Packages.props, are deliberately left unchanged.