Dashboard › cli › Dependency-update PR workflow
Dependency-update PR workflow
Category: preference
Confidence: 1.00
ID: 01a08a9c-b4e1-7a2e-a0e7-f11bf8147d9d
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 1
Source session: 0HM0fc1YdkpDO2vLs
Created: 2026-09-10 09:18:40
Updated: 2026-09-10 09:18:40
Cross-Project Recalls
Content
Chose the regular PR workflow over direct updates or silently replacing Dependabot PRs because dependency changes need auditable, minimal diffs.
Steps:
- Inspect
package.json and lockfile diffs — confirm peer ranges and reject unrelated churn.
- Create a properly named branch and commit intended changes, including
.lore.md — flag unintended generated changes.
- Verify remote tracking, push the correct branch, and open the PR immediately.
- Require green CI, rerun flaky jobs, and apply the immutable merge gate [[01a08a72-1dec-7485-b840-461bef48aac8]].
- Close replaced or duplicate PRs, then merge only when clean.
Gotchas:
- Fork-only artifacts look sufficient but can be inaccessible; keep review artifacts base-repository fetchable [[01a08a6f-926b-7b29-ac24-6db25845894d]].
Verify:
- [ ] Peer dependencies resolve.
- [ ] No duplicate PR remains open.