Skip to content
ci

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

Sign in to view logs

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 #554

Triggered via pull request August 6, 2025 20:01
@meck93meck93
synchronize #311
meck93:310-middleware-no-parent-route
Status Success
Total duration 3m 13s
Artifacts –

ci.yml

on: pull_request
ci
1m 6s
ci
ci-windows
3m 9s
ci-windows
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>0yLSTaAAAAAAefoe1LLXqSIhflRwmd7+3Q0hJMzBFREdFMDQxNwBFZGdl
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>0Q7WTaAAAAAA+9+Civ0yHRKXKwUVV/EC4Q0gxRURHRTIxMTgARWRnZQ==
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