chore(ci): make build-copr.sh the single source of truth for COPR chroots

[jdx]

Summary

The COPR publish workflow hardcoded the chroot list in two places (the workflow_dispatch input default and the release-event branch) and always passed --chroots to build-copr.sh, so the script's own default CHROOTS= was unreachable. Any change to the chroot list had to be made in three files to actually take effect — a footgun that caused PR #9787's EL9 chroots to be set as a no-op until this lands.

Refactored to make packaging/copr/build-copr.sh:9 the single source of truth:

• workflow_dispatch.chroots input default changed from the hardcoded list to "", with a description that explains the empty-string semantics.
• Removed the release-event branch's hardcoded CHROOTS=... line entirely.
• The build step now passes --chroots only when the workflow input was explicitly set (non-empty); otherwise the script falls through to its own default list.
• Switched the build step to a bash array for readable conditional arg passing.

After this, both the release-event path and the no-input workflow_dispatch path use whatever packaging/copr/build-copr.sh declares.

Test plan

• actionlint .github/workflows/copr-publish.yml passes locally.
• Next workflow_dispatch with empty input → COPR job logs the script default list (currently includes epel-10-* and centos-stream+epel-next-9-* after chore(copr): publish EL9 builds via centos-stream+epel-next-9 chroot #9787 lands).
• Next workflow_dispatch with a custom value → COPR job logs that value instead.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes the COPR publish workflow’s chroot selection logic, which can alter what targets get built on release/publish runs. Risk is limited to CI/release automation but could result in missing or unintended COPR builds if the default list or input handling is wrong.

Overview
Makes packaging/copr/build-copr.sh the single source of truth for COPR chroots by removing the workflow’s hardcoded/default chroot list and only setting CHROOTS when workflow_dispatch provides a non-empty input.

Refactors the COPR submission step to build a bash args array and conditionally append --chroots, so release-triggered runs (and empty-input manual runs) fall back to the script’s internal default chroot list.

^{Reviewed by Cursor Bugbot for commit 454b531. Bugbot is set up for automated code reviews on this repo. Configure here.}

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[greptile-apps]

Greptile Summary

This PR eliminates the three-way chroot list duplication between copr-publish.yml (dispatch default, release branch) and build-copr.sh. Both the release-event path and a no-input workflow_dispatch now fall through to the script's own CHROOTS default on line 9, while an explicit dispatch input still overrides it.

• The workflow_dispatch chroots input default is changed to "", and the step that previously set a hardcoded CHROOTS= for the release event is removed entirely.
• --chroots is now appended to the invocation only when $CHROOTS is non-empty (i.e., an explicit dispatch override), using a bash args array for clarity.

Confidence Score: 5/5

The change is safe to merge; it simplifies a straightforward CI workflow with no logic regressions on any trigger path.

The refactoring is minimal: one file changed, the conditional logic correctly distinguishes all three trigger paths (release, dispatch-with-input, dispatch-without-input), and the bash array approach is a strict improvement over the previous single-line invocation. The script's own default list is now reachable as intended.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/copr-publish.yml	Refactored to remove duplicate chroot lists; build-copr.sh is now the single source of truth via conditional --chroots injection only when explicitly set by the caller.

_{Reviews (1): Last reviewed commit: "chore(ci): make build-copr.sh the single..." | Re-trigger Greptile}

[github-actions]

Hyperfine Performance

mise x -- echo

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.5.6 x -- echo	20.5 ± 1.0	18.5	27.7	1.00
mise x -- echo	20.5 ± 0.9	18.6	27.2	1.00 ± 0.07

mise env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.5.6 env	19.8 ± 1.0	17.7	26.8	1.00
mise env	20.0 ± 1.2	18.1	29.8	1.01 ± 0.08

mise hook-env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.5.6 hook-env	21.0 ± 1.0	18.6	27.7	1.00
mise hook-env	21.0 ± 0.9	19.1	27.8	1.00 ± 0.07

mise ls

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2026.5.6 ls	17.3 ± 0.9	15.5	23.7	1.00
mise ls	17.3 ± 0.9	15.6	26.0	1.00 ± 0.07

xtasks/test/perf

Command	mise-2026.5.6	mise	Variance
install (cached)	130ms	130ms	+0%
ls (cached)	60ms	59ms	+1%
bin-paths (cached)	65ms	65ms	+0%
task-ls (cached)	496ms	495ms	+0%