[caarlos0]

Tell users how to fix an AUR entry that gets two archives for the same architecture.

ErrMultipleArchivesSameArch (added in #7100) rejects configs that previously produced output. It is reachable with a plain archives: [{formats: [tar.gz, zip]}] plus an aurs entry without ids: both linux/amd64 archives pass the ByTypes(UploadableArchive, UploadableBinary) filter.

The old PKGBUILD emitted two source_x86_64= lines. That is valid bash — the last one wins — but the archive pipe builds formats concurrently, so which format shipped was not deterministic. Rejecting the config is still the right call; this only makes the fix discoverable.

ids alone is not enough, though. The archive pipe stamps every format of a single archives entry with the same ExtraID (archive.go:259), so artifact.ByIDs cannot separate them — a user who follows a bare "use ids" hint adds ids and hits the identical error. The message therefore names both causes:

one aur can handle only one archive of each architecture. Consider using ids in the aurs section; if a single archives entry produces multiple formats, split it into separate archives with distinct ids

TestRunPipeRejectsDuplicateArchitectures gains two rows — single id, multiple formats and single id, multiple formats, filtered by ids — the second of which records that ids does not disambiguate that case. The assertion also moves from the literal string to require.ErrorIs on the sentinel, matching brew and cask, so future wording changes no longer require a test change.

Follow-up to #7100. Part of a series of fixes found reviewing v2.18.1..main.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.56%. Comparing base (7ba40dc) to head (af2ccf9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7141   +/-   ##
=======================================
  Coverage   91.56%   91.56%           
=======================================
  Files         191      191           
  Lines       15903    15903           
=======================================
  Hits        14562    14562           
  Misses       1341     1341           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[caarlos0]

Verdict: one blocking problem

(Posted as a comment: GitHub does not permit a change request on your own pull request.)

The one goal of this change is to make the fix discoverable. For the configuration that the description names as the cause (archives: [{formats: [tar.gz, zip]}] with no ids), the new advice does not work. See the comment on internal/pipe/aur/aur.go:37.

The change itself is correct and safe in all other respects:

• The rejection is still the correct behavior. The old PKGBUILD emitted two source_x86_64= lines, and the artifact order is not deterministic, thus the shipped format was random.
• Nothing else in the repository, the documentation, or the golden testdata asserts the old string.
• golangci-lint reports 0 issues. The message does not start with a capital letter and does not end with punctuation, thus ST1005 is satisfied.

Missing coverage (no single line)

The scenario in the description — one archives entry, two formats, one shared artifact ID — has no test in the repository. TestRunPipeRejectsDuplicateArchitectures covers only artifacts with different IDs. A test for that scenario would have shown that the new advice is inert.

Verification gaps

• The claim that the pre-#7100 PKGBUILD was valid bash is confirmed by a template trace (tmpl.go:65-67), not by a build of the old tree.
• TestRunPipeMultipleConfigurations fails locally because of a safe.bareRepository=explicit git setting. That failure is environmental. With safe.bareRepository=all, go test ./internal/pipe/aur/... passes.

---

This review was produced by an automated reviewer (GitHub Copilot CLI).

[cloudflare-workers-and-pages]

Deploying goreleaser with    Cloudflare Pages

Latest commit:	af2ccf9
Status:	✅  Deploy successful!
Preview URL:	https://9faaf551.goreleaser.pages.dev
Branch Preview URL:	https://fix-aur-duplicate-arch-hint.goreleaser.pages.dev

View logs