chibi-scheme's manifest returns 404 somehow on bottle install

[raviqqe]

Output of brew config

> brew config
HOMEBREW_VERSION: 4.4.4-7-gcf06bfd
ORIGIN: https://github.com/Homebrew/brew
HEAD: cf06bfd79760e4623e401a5056a8b1d129e648d8
Last commit: 3 hours ago
Core tap JSON: 05 Nov 01:02 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0
HOMEBREW_EDITOR: nvim
HOMEBREW_MAKE_JOBS: 20
HOMEBREW_NO_EMOJI: set
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.3.5 => /home/linuxbrew/.linuxbrew/Cellar/ruby/3.3.5/bin/ruby
CPU: 20-core 64-bit unknown_0x6_0xba
Clang: 19.1.3
Git: 2.47.0 => /home/linuxbrew/.linuxbrew/bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 6.8.0-45-generic x86_64 GNU/Linux
OS: Ubuntu 22.04.5 LTS (jammy)
Host glibc: 2.35
/usr/bin/gcc: 11.4.0
/usr/bin/ruby: 3.0.2
glibc: N/A
gcc@11: N/A
gcc: 14.2.0_1
xorg: N/A

Output of brew doctor

> brew doctor
Your system is ready to brew.

Description of issue

Installing chibi-scheme via bottles seem to fail right now with the following erroneous outputs, at least, on Linux:

> brew install chibi-scheme
==> Downloading https://ghcr.io/v2/homebrew/core/chibi-scheme/manifests/0.11.0
curl: (22) The requested URL returned error: 404

==> Fetching chibi-scheme
==> Downloading https://ghcr.io/v2/homebrew/core/chibi-scheme/blobs/sha256:395662059e73c41bc156117acff16a06d156e785d8dd
################################################################################################################ 100.0%
==> Verifying attestation for chibi-scheme
Warning: Failed to verify attestation. Retrying in 1s...
Warning: Failed to verify attestation. Retrying in 3s...
Warning: Failed to verify attestation. Retrying in 9s...
Warning: Failed to verify attestation. Retrying in 27s...
Warning: Failed to verify attestation. Retrying in 81s...
Error: The bottle for chibi-scheme has an invalid build provenance attestation.

This may indicate that the bottle was not produced by the expected
tap, or was maliciously inserted into the expected tap's bottle
storage.

Additional context:

no attestation matches subject: chibi-scheme--0.11.0.x86_64_linux.bottle.tar.gz

Something weird is that this has worked for a long time. I'm not sure if I should file a bug for this. The formula has been in this situation for a few days his might be just a temporary outage of the infrastructure.

Can anyone reproduce the problem or know how to re-trigger bottle builds to fix it?

[SMillerDev]

There is an issue already for build attestation failures. It's GitHub infrastructure failing, not much we can do unfortunately