maintaining-dependency-patches

Automate patch management for local dependency patches across patching tools.

357|255|Updated Nov 1, 2019
One-click install
npx skills add https://github.com/Agoric/agoric-sdk --skill maintaining-dependency-patches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintaining-dependency-patches
Source: https://github.com/Agoric/agoric-sdk/tree/main/.agents/skills/maintaining-dependency-patches
Command: npx skills add https://github.com/Agoric/agoric-sdk --skill maintaining-dependency-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinate and sustain local patches against installed dependencies across package managers, ensuring patches remain viable as upstream fixes and version bumps occur.

Core Features & Use Cases

  • Patch tracking and disposition: record upstream issues/PRs and patch status for each patch in the stack.
  • Drift detection and forward-porting: re-apply patches when dependencies bump and retire them when upstream fixes render them unnecessary.
  • Ecosystem coverage: supports patch-package, composer-patches, and Bazel patching workflows across JS, PHP, and polyglot environments.

Quick Start

Audit the patch stack, bump a dependency, and re-apply patches against the updated source.

Frequently Asked Questions about maintaining-dependency-patches

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

FAQPage Schema
How do I keep local dependency patches in sync with upstream version bumps?

Detecting patch drift involves comparing your local dependency patches against the updated upstream source after a dependency bump. This Skill automates drift detection and forward-ports patches to ensure they remain viable across package managers.

Does this dependency patch management workflow support Bazel and composer-patches?

Yes, the dependency patch management workflow supports Bazel patching, composer-patches, and patch-package. It operates across JS, PHP, and polyglot environments to coordinate local patches against installed dependencies.

What is the best way to automate forward-porting local patches during dependency updates?

The best way to automate forward-porting is to audit the patch stack and re-apply patches against the updated source. This process tracks patch disposition and retires patches automatically when upstream fixes are released.

When do I need to retire a local dependency patch from my stack?

You need to retire a local dependency patch when an upstream fix renders it unnecessary. The patch tracking system records upstream PRs and patch status to identify when local modifications are no longer required.

How do I track the upstream disposition of a patch applied via patch-package?

To track upstream disposition for patch-package modifications, you record the associated upstream issues and PRs for each patch in the stack. This maintains a clear status of whether the patch is still needed or can be retired.