skills.rest
vesviet
vesvietCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

upgrade-common-lib

Upgrade the common library version across Go microservices in go.mod files.

Updated Feb 10, 2026
Search Tags:#dependency management#microservices#go#version upgrade#build verification#common library
One-click install
npx skills add https://github.com/vesviet/microservices-agent-skills --skill upgrade-common-lib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade-common-lib
Source: https://github.com/vesviet/microservices-agent-skills/tree/main/skills/upgrade-common-lib
Command: npx skills add https://github.com/vesviet/microservices-agent-skills --skill upgrade-common-lib

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating the shared common library across multiple microservices, ensuring version consistency and preventing dependency drift after a new common library tag is released.

Core Features & Use Cases

  • Bulk Version Updates: Automatically updates go.mod files to the latest common library version.
  • Dependency Management: Handles updating other ta-microservices dependencies and tidies the module.
  • Build Verification: Ensures all services build successfully after the upgrade.
  • Use Case: After tagging a new version of your core common library, use this skill to systematically update all dependent microservices, verify their builds, and commit the changes.

Quick Start

Use the upgrade-common-lib skill to update all services that import common to the latest version.

Frequently Asked Questions about upgrade-common-lib

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

FAQPage Schema
How do I upgrade a common Go library version across multiple microservices?▼

To upgrade a common Go library across microservices, automate bulk go.mod file updates to the latest version, tidy modules, remove conflicting replace directives, and verify build integrity for each service.

What is dependency drift in Go microservices and how do I fix it?▼

Dependency drift occurs when Go microservices use inconsistent common library versions. Fix version drift by systematically updating all dependent services to the latest tagged release and verifying their builds.

How do I remove conflicting replace directives in go.mod during a dependency upgrade?▼

When upgrading common library dependencies, remove conflicting replace directives from go.mod files automatically during the bulk update process to ensure clean module tidying and successful build verification.

Can I verify build integrity for multiple Go services after a common library update?▼

Yes, build verification ensures all Go microservices build successfully after a common library update. This systematic check confirms that dependency changes and removed replace directives do not break existing service builds.

Does this common library upgrade approach work with other ta-microservices dependencies?▼

Yes, the dependency management process handles updating other ta-microservices dependencies alongside the common library. It automatically tidies the Go module to ensure all shared code dependencies remain consistent.

Related Skills

Explore More Software Engineering Skills→
kaptinlinkaptinlin
23

multimodule-initializing

Initialize or convert Go libraries into multi-module repositories with go.work.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
NagyViktNagyVikt
2

triage-go-vulnerabilities

Analyze Go dependency vulnerabilities with govulncheck and map remediation strategies.

Community
Intermediate
authgearauthgear
2.0k

update_go_version

Update Go version references across go.mod, Dockerfiles, and Nix tooling.

Official
Intermediate