dependency-update

Update Gradle dependency version constants in Kotlin objects and generate a Markdown report.

2|Updated May 28, 2021
One-click install
npx skills add https://github.com/SpineEventEngine/validation --skill dependency-update-spineeventengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-update
Source: https://github.com/SpineEventEngine/validation/tree/main/.agents/skills/dependency-update
Command: npx skills add https://github.com/SpineEventEngine/validation --skill dependency-update-spineeventengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps your build dependencies up to date by automatically discovering the latest accepted versions and applying them to the dependency version constants in your repository, without requiring manual lookup.

Core Features & Use Cases

  • Scans and updates dependency objects: Walks all Kotlin dependency declarations under buildSrc/src/main/kotlin/io/spine/dependency/ and updates the relevant version constants in place.
  • Resolves latest accepted versions: Uses the URL hints found in each dependency file (or Maven metadata fallbacks) to determine what counts as the latest accepted release for each artifact.
  • Handles snapshot/pre-release policy: Enforces “released only” for external scopes while allowing snapshots and pre-releases for local/ Spine SDK artifacts, based on Maven metadata rules.
  • Produces a structured update report: Summarizes what changed, what was already current, what needs manual review, and which pre-releases were filtered out.

Quick Start

Run dependency-update in your repo to scan buildSrc dependency declarations and update version constants to the latest accepted versions.

Frequently Asked Questions about dependency-update

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

FAQPage Schema
How do I update dependency versions in a Gradle buildSrc Kotlin project?

To update dependency versions in a Gradle buildSrc Kotlin project, this Skill scans dependency declarations under buildSrc and automatically updates version constants in place. It discovers the latest accepted artifact versions using file URL hints or Maven metadata fallbacks.

How does pre-release filtering work when updating Maven artifact versions?

Pre-release filtering enforces released-only version upgrades for external dependencies by excluding pre-releases, while allowing snapshots and pre-releases specifically for local Spine SDK artifacts based on Maven metadata rules.

Can I automate dependency updates for a Protobuf Java-Kotlin codebase with centralized version constants?

Yes, you can automate dependency updates for a Protobuf Java-Kotlin codebase. It applies to projects that centralize dependency versions in Kotlin objects, parsing object-level Maven coordinates to update version literals with anchored replacements.

What is the best way to report major version bumps when refreshing Gradle dependencies?

The best way to report major version bumps when refreshing Gradle dependencies is through a comprehensive Markdown report. This report summarizes changes, current versions, manual review needs, and includes major-bump safety flags.

Why are my snapshot dependencies not updating to the latest released versions?

Snapshot dependencies might not update to the latest released versions because the update process enforces a strict pre-release filtering policy. It restricts external scopes to released-only upgrades while only allowing snapshots for local Spine SDK artifacts.