Merge Renovate development dependencies through a pull request #115
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!115
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-protect-main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #79 and #77. This lands before branch protection is switched on.
Renovate's development-dependency group used
automergeType: "branch", which pushes straight tomain. Protection refuses that, and exempting Renovate would let one writer past the e2e gate. Now:automergeType: "pr",platformAutomerge: true(Forgejo'smerge_when_checks_succeed) andautomergeStrategy: "fast-forward". On the pinned 44.105.2 that maps to Forgejo'sfast-forward-only(renovatebot/renovate#46203, which is behind that tag by 132 commits, so included).prBodyNotes: ["## Changelog\nNONE"]for this rule only. A dev-dependency bump never changes what a user sees. Every other Renovate PR gets no note and fails the release-note check until a person writes one. The check stops at Renovate's own---/### Release Notes, so upstream notes are never read as ours (tested in #113).Validated with
renovate-config-validator44.105.2 as repo config.Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt
da3cef0b68cb4f0b5c87cb4f0b5c87b5baae4741