githubnext / githubnext/gh-aw-cao
[dependabot:release-train-updater] npm security fix ready but create_pull_request failed again (undici override, 3rd consecutive failure)
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
`create_pull_request` failed twice this run with `{"result":"error","error":"No changes to commit - no commits found"}` despite a valid, verified local commit — the same failure mode documented in the 2026-09-10 07:55 UTC run's issue for this repo. The prepared fix is ready to apply manually or via a fresh workflow attempt once the underlying tool bug is resolved.
### Prepared fix (ready to apply)
- **Manifest(s):** `package.json`, `package-lock.json`
- **Change:** add `"overrides": { "undici": "6.28.1" }` to root `package.json`, then run:
```
npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts
```
- **Root cause:** root devDependency `@actions/github@^7.0.0` and the nested copy pulled in by `@actions/artifact` → `@actions/github@6.0.1` both resolve `undici@^5.28.5`, landing on vulnerable `5.29.0`.
- **Diff size:** `package.json` +3/-0, `package-lock.json` net +41/-34 (undici bump + removal of now-unused `@fastify/busboy`, an undici@5.x-only transitive dep).
- **Scope:** devDependency-only (`activity/local-runner.mjs` local Actions tooling), not production runtime. `dashboard/site/package.json` has an independent lockfile and is unaffected.
### Advisories fixed by this override
- GHSA-g9mf-h72j-4rw9 (high) — unbounded decompression chain / resource exhaustion
- GHSA-2mjp-6q6p-2qxm — request smuggling
- GHSA-vrm6-8vpv-qv8q
- GHSA-v9p9-hfj2-hcw8 — WebSocket DoS/exceptions
- GHSA-4992-7rv2-5pvq — CRLF injection
### Validation performed this run
- `npm audit --package-lock-only --json` before: 5 vulnerabilities (1 high, 4 moderate).
- After applying the override and regenerating the lockfile: **0 vulnerabilities**.
- Both files confirmed valid JSON.
- `git diff origin/main HEAD --stat` confirmed exactly the 2 expected files changed.
- Local commit `11e1fdab` on branch `dependabot-agent/undici-security-fix-20260910103359` verified present via `git log origin/main..HEAD` (1 commit) immediately before both `create_pull_request` attempts.
### This run's `create_pull_request` attempts
1. Attempt 1 (title/branch/base/body): `{"result":"error","error":"No changes to commit - no commits found"}`
2. Attempt 2 (title/branch/body, no explicit `base`): identical error.
This is at least the **third** consecutive run to report this same "No changes to commit" failure for a valid, small, verified commit against this repository's `create_pull_request` safe-output path — see the 2026-09-10 07:55 UTC cache entry for the first two attempts (commit `a55c2420`, branch `dependabot-agent/undici-security-fix-20260910075319`). This is not a diff-size issue (all three diffs were small, 30-75 line changes). This strongly suggests a bug specific to this repository/workflow's `create_pull_request` tool pipeline, independent of the ENOBUFS root-cause fix referenced in unrelated cross-repo cache entries.
### Recommended next steps
1. Investigate the `create_pull_request` safe-output tool/pipeline for `githubnext/gh-aw-cao` specifically — three consecutive failed attempts with a verified, non-empty commit is a strong signal of a systemic bug (not diff size, not ENOBUFS).
2. Once resolved, re-apply the override above (or check whether the fix has already landed elsewhere) and confirm `npm audit` returns 0 vulnerabilities.
3. Manual apply is trivial in the meantime: add the `overrides.undici` entry shown above to `package.json` and regenerate `package-lock.json`.
### Control Plane
- Correlation ID: 34465727933-181
- Central repo: githubnext/gh-aw-cao
- Run URL: https://github.com/githubnext/gh-aw-cao/actions/runs/34465727933
> Generated by [:dependabot: Dependabot / Release Trains](https://github.com/githubnext/gh-aw-cao/actions/runs/34466176331) · copilot · auto · 78.6 AIC · ⌖ 9.54 AIC · ⊞ 18K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Fdependabot-release-train-updater%22&type=issues)
>
Add this agentic workflow to your repo
To install this agentic workflow, run
```
gh aw add githubnext/gh-aw-cao/.github/workflows/dependabot-release-train-updater.md@main
```
> - [x] expires on Sep 24, 2026, 10:37 AM UTC
Contributor guide
Research direction
Start by reviewing the create_pull_request safe-output path for githubnext/gh-aw-cao and the dependabot-release-train-updater workflow, using the reported commit 11e1fdab and repeated no-changes error as the reproduction. Check package.json and package-lock.json for the prepared undici override, then verify that the workflow can create a pull request and that npm audit --package-lock-only --json reports zero vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, nodejs
- Domain
- devops, security, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100