Skip to content

fix(#3533): replace stale quick-build-args.conf with empty string - #3534

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3533-fix-build-args-conf
Open

fix(#3533): replace stale quick-build-args.conf with empty string#3534
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/3533-fix-build-args-conf

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

What:

Replace the stale quick-build-args.conf reference in hack/release-branch-pipeline-patch.sh with an empty string (""), matching the pattern already used for main-build-args.conf on the next line.

Why:

The awk gsub that transforms main-pre-merge-build-args.conf was replacing it with quick-build-args.conf, a file that does not exist in the repository. This caused every release branch setup PR to produce incorrect pipeline YAML that required manual correction. Both human reviewer (simonbaird) and the review agent independently flagged this on PR #3529.

Tickets:


Closes #3533

Post-script verification

  • Branch is not main/master (agent/3533-fix-build-args-conf)
  • Secret scan passed (gitleaks — af3fe00e4120446b6a808687cc3a5af96ce3d779..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

The awk gsub on line 64 of release-branch-pipeline-patch.sh
replaced main-pre-merge-build-args.conf with
quick-build-args.conf, a file that does not exist in the
repository. This caused the generated pull-request pipeline
YAML to reference a non-existent build-args-file, requiring
manual correction on every release branch PR.

Change the replacement to empty string ("") to match the
pattern already used on line 65 for main-build-args.conf,
and to match what PR authors have been manually correcting
to on the v0.8 and v0.9 release branches.

Note: pre-commit could not run (network restriction
prevented fetching the conforma/hooks repo). The only
configured hook (check-commit-message) applies to commit
messages, not file content.

Closes #3533
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Sep 2, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 2, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:18 PM UTC · Completed 7:30 PM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.95

@fullsend-ai-review fullsend-ai-review Bot added the risk/low PR risk: low label Sep 2, 2026
@fullsend-ai-review

Copy link
Copy Markdown

Risk Assessment: low (1/5)

Details

Minimal single-line bug fix in a rarely-touched hack script, replacing a stale file reference with an empty string; scope perfectly matches the linked issue with no security, dependency, or CI impact.

@fullsend-ai-review

Copy link
Copy Markdown

Looks good to me

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Sep 2, 2026
@codecov

codecov Bot commented Sep 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
acceptance 54.46% <ø> (ø)
generative 12.27% <ø> (ø)
integration 23.59% <ø> (ø)
unit 72.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge ready-for-review Triggers review agent dispatch risk/low PR risk: low size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix stale quick-build-args.conf reference in release-branch-pipeline-patch.sh

0 participants