Skip to content

fix: fixes middleware not being applied inside nested folder where the parent folder has no route #555

fix: fixes middleware not being applied inside nested folder where the parent folder has no route

fix: fixes middleware not being applied inside nested folder where the parent folder has no route #555

Triggered via pull request August 6, 2025 20:19
Status Success
Total duration 2m 22s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 1 notice
ci
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0JLmTaAAAAAAVttu6KrdoQ6bmttbk5k/XQ0hJMzBFREdFMDQxNwBFZGdl
ci
Failed to restore: Cache service responded with 400
ci-windows
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0armTaAAAAADcem0zi1fMT5D1LZIoWJYMRE0yRURHRTA3MjAARWRnZQ==
ci-windows
Failed to restore: Cache service responded with 400
ci-windows
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677