The "Dependency Cutout" Workflow Pattern
12 days ago
- #dependency-management
- #software-development
- #open-source
- Common bad solutions to dependency bugs include switching libraries, vendoring, monkey-patching, workarounds, or waiting for upstream fixes.
- The ideal workflow involves reporting the issue, forking the library, setting up CI, fixing the bug locally, deploying internally, proposing changes upstream, and eventually unwinding the fork.
- Corporate and open-source incentive structures often discourage proper upstream contributions.
- Steps include clear issue reporting, maintaining a temporary fork with proper CI, local testing, internal deployment, upstream PR, and finally reverting to the official release.