NEC-375: Renovate failures - investigate #339
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
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!339
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-375-renovate-failures-investigate"
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?
Task: NEC-375 — https://projectron.nerchure.com/tasks/397
Renovate itself has been healthy on every run; what failed were the checks on its pull requests. (A) The release-note job passed the pull request body through the environment, and Linux refuses one environment string of 128 KiB or more, so on Renovate's 250 KB bodies (#320, #337) the step died at exec with 'argument list too long' before node started, and the NEC-353 hold never ran either. Both scripts now read the body from the runner's event file (GITHUB_EVENT_PATH) and exit 2 when they cannot see it; a test spawns them on a 300,000-byte body, and a scan refuses any github.event reference in .forgejo that is not a named short scalar. (B) Only development dependencies carried a '## Changelog NONE', so Renovate's own image bump (#320) waited for a note nobody could keep in a body Renovate rewrites: action refs, the Renovate image and the Obsidian e2e pin now carry NONE, and scripts/renovate-config.test.mjs refuses NONE on any rule that can match something shipped. (C) Development majors were a batch of their own; #337 held fourteen and TypeScript 7 dropping baseUrl kept every one out. They now arrive one pull request each (monorepo families together), under renovate/dev-, never automerged. Review with Renovate's own rule matching found that without that prefix a package that is dev in one workspace and production in another (ws, yjs) shared a branch and the production major inherited NONE; fixed and tested. Also: the 'dependencies' and 'security' labels renovate.json asks for did not exist and were created; the TypeScript 7 migration is filed as NEC-376; and as a ride-along NEC-377, e2e.yml's push trigger now excludes renovate/**, since Renovate's rebases made main's own edits to its paths count as the branch's (three runs on 26 Oct). Verified by a probe pair: the same head started e2e.yml on this branch (run 1664) and not on renovate/nec-375-probe. Not verifiable until Renovate's next run on Monday 9 Nov: the notes Renovate actually writes, #337 autoclosing, #320 gaining its note.
Spec:
docs/changes/NEC-375-renovate-failures/spec.mdAlso fixes NEC-377: e2e.yml runs on Renovate rebases despite its paths filter
Changelog
NONE