You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automate upstream update tracking for vendored skills #254
Humanizer was added as a minimal, SHA-pinned vendored skill in #249. Updating it currently requires manually noticing an upstream release and copying the reviewed files again. Other manually vendored skills need the same maintenance path.
Goal
Use Renovate where practical to notify maintainers of upstream updates and open reviewable update or reminder PRs, without silently replacing vendored content or misrepresenting its provenance.
Acceptance criteria
Inventory manually vendored skills and record their upstream repository, source paths, version/tag and immutable commit SHA. Avoid duplicating tracking already provided by existing APM dependency updates.
Integrate with Renovate, reusing existing shared configuration where applicable, to detect new stable releases or upstream commits when releases are unavailable.
Keep any proposed upstream target separate from the recorded vendored version/SHA until the corresponding files have actually been updated and reviewed.
Document the re-vendoring procedure: retain only required skill files, preserve licenses, update THIRD_PARTY_NOTICES.md, provenance/hashes and relevant documentation, and regenerate indexes when needed.
Route content updates through the existing external-primitives review and SkillSpector gates. Reassess changed findings and stale acceptances; do not broaden suppressions or automerge vendored updates.
Verify tracking with offline fixtures or a dry run. Discovering an update must not execute upstream skill code.
Initial example
blader/humanizer v4.0.0, commit b48c832f0f809c1b5658edbb838c2521b72f2413, bundled at .apm/skills/humanizer/.
Activity