You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Failed to install coveralls via Homebrew (macOS) #262
Run 5cbfd81
Run echo "Warning: The coverage-reporter-platform parameter is not available on macOS. The default version for macOS will be used." >&2
Warning: The coverage-reporter-platform parameter is not available on macOS. The default version for macOS will be used.
Run # Enable debugging if 'debug' is true
Warning: Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.
Warning: Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.
Warning: Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.
==> Fetching downloads for: coveralls
✔︎ Bottle Manifest bdw-gc (8.2.12)
✔︎ Bottle Manifest ca-certificates (2025-12-02)
✔︎ Bottle Manifest openssl@3 (3.6.1)
✔︎ Bottle Manifest sqlite (3.51.2_1)
✔︎ Bottle bdw-gc (8.2.12)
✔︎ Bottle ca-certificates (2025-12-02)
✔︎ Bottle sqlite (3.51.2_1)
✔︎ Bottle coveralls (0.6.17)
✔︎ Bottle openssl@3 (3.6.1)
==> Installing coveralls from coverallsapp/coveralls
==> Installing dependencies for coverallsapp/coveralls/coveralls: bdw-gc, ca-certificates, openssl@3 and sqlite
==> Installing coverallsapp/coveralls/coveralls dependency: bdw-gc
==> Pouring bdw-gc--8.2.12.arm64_sequoia.bottle.tar.gz
🍺 /opt/homebrew/Cellar/bdw-gc/8.2.12: 82 files, 1.9MB
==> Installing coverallsapp/coveralls/coveralls dependency: ca-certificates
==> Pouring ca-certificates--2025-12-02.all.bottle.1.tar.gz
==> Regenerating CA certificate bundle from keychain, this may take a while...
🍺 /opt/homebrew/Cellar/ca-certificates/2025-12-02: 4 files, 236.4KB
==> Installing coverallsapp/coveralls/coveralls dependency: openssl@3
==> Pouring openssl@3--3.6.1.arm64_sequoia.bottle.tar.gz
Error: Could not symlink bin/openssl
Target /opt/homebrew/bin/openssl
is a symlink belonging to openssl@1.1. You can unlink it:
brew unlink openssl@1.1
To force the link and overwrite all conflicting files:
brew link --overwrite openssl@3
To list all files that would be deleted:
brew link --overwrite openssl@3 --dry-run
Failed to install coveralls via Homebrew (macOS).
Error: Process completed with exit code 1.
The full macOS chain — published @v2 → Homebrew formula → coverage-reporter 0.6.17 → report upload — is now verified end-to-end by a cross-platform smoke test on both macos-15 and macos-latest images, using the same arm64_sequoia bottle shown in your log.
Note the pinned SHA in your log (5cbfd81 = v2.3.7) now fails on updated runners for an unrelated reason: Homebrew 6 refuses untrusted taps (Installation fails on macOS with recent Homebrew changes #264). Please move to coverallsapp/github-action@v2 (or pin ≥ v2.3.8).
To be transparent: the exact cause of the April failure was never pinned down, so this close is "cannot reproduce on current versions + the install path has since changed," not a targeted fix. If you still hit it on v2.3.8, reopen with the full log tail and we'll dig in.
Activity
afinetooth commentedon Apr 27, 2026
Hi, @amilcarlucas. Thanks for reporting. We're looking into it.
Similar/related issue: #248
0.6.17But this use case is installing
0.6.17.afinetooth commentedon Jul 27, 2026
Closing as resolved-by-upgrade — please reopen if it persists on the current version.
Since this report:
brew install coverallsapp/coveralls/coveralls, as required by Homebrew 6's new tap trust.@v2→ Homebrew formula → coverage-reporter 0.6.17 → report upload — is now verified end-to-end by a cross-platform smoke test on bothmacos-15andmacos-latestimages, using the samearm64_sequoiabottle shown in your log.5cbfd81= v2.3.7) now fails on updated runners for an unrelated reason: Homebrew 6 refuses untrusted taps (Installation fails on macOS with recent Homebrew changes #264). Please move tocoverallsapp/github-action@v2(or pin ≥ v2.3.8).To be transparent: the exact cause of the April failure was never pinned down, so this close is "cannot reproduce on current versions + the install path has since changed," not a targeted fix. If you still hit it on v2.3.8, reopen with the full log tail and we'll dig in.