[ci]: continue-on-error for more gh auth status checks#90890
Conversation
Failing test suitesCommit: ef8ae85 | About building and testing Next.js
Expand output● deterministic build - changing deployment id › build output API - cacheComponents builder › should produce identical build outputs even when changing deployment id
Expand output● server-components-hmr-cache › should support reading from an infinite streaming fetch |
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **401 kB** → **401 kB** ✅ -31 B80 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URL |
I'd keep it since it's still helpful debugging. We originally added it after we got confused why release was failing only to find out the token was expired. Ideally GH would just fix it because early errors save time. |
This seems to be failing for our deploy test workflow ([x-ref](https://github.com/vercel/next.js/actions/runs/22685809647/job/65778800145)). Updating to `continue-on-error` similar to #89098 because this check doesn't seem reliable. If it fixes, will just remove in both spots all together.

This seems to be failing for our deploy test workflow (x-ref).
Updating to
continue-on-errorsimilar to #89098 because this check doesn't seem reliable.If it fixes, will just remove in both spots all together.