mirror of
https://github.com/andrewyng/openworker.git
synced 2026-09-14 00:00:58 +00:00
Rohit C Prasad
b5b000eb76
Security, Cloud Posture, and Dependency Audit coworkers as self-contained bundle dirs (manifest + skills) driving OSS scanners; registry loads bundle subdirs; packaging includes them.
1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| safe-upgrade-pr | Ship minimal, test-verified dependency upgrades as focused PRs |
Turn triaged advisories into upgrade PRs a reviewer can merge without fear.
- One branch per ecosystem (
security/deps-npm,security/deps-python), smallest viable bumps: the fixed-in patch/minor, not "latest". Majors get their own branch and a migration note. - Regenerate lockfiles with the repo's OWN toolchain (
npm install pkg@ver,uv lock,poetry update pkg…) — never hand-edit a lockfile. - Verify before proposing: clean install, build, and the project's test suite. Red suite → investigate; if the bump itself breaks the build, document what's entangled and propose the next-smallest path instead of forcing it.
- PR body per upgrade: advisory id(s) closed, package old→new version, reachability verdict from the audit (one line), and the verification commands run. Skip CVE boilerplate walls — link the advisory instead.
- Leave
accept-with-noteadvisories OUT of the PR; record them in the PR body's "consciously not fixed" list with their justification, so the decision is visible and revisitable. - Never merge your own upgrade PR — deliver it with what a reviewer should check (typically: lockfile diff sanity and the test run).