Skip to content
ci

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

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

Triggered via pull request August 6, 2025 09:59
@meck93meck93
opened #311
meck93:310-middleware-no-parent-route
Status Failure
Total duration 2m 56s
Artifacts –

ci.yml

on: pull_request
ci
55s
ci
ci-windows
2m 52s
ci-windows
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 2 warnings, and 1 notice
ci
Process completed with exit code 1.
test-integration/apps.test.ts > Nested Middleware > Should apply grandparent middleware to child index route - /without-route/with-index: test-integration/apps.test.ts#L486
AssertionError: expected null to deeply equal 'true' - Expected: "true" + Received: null ❯ test-integration/apps.test.ts:486:63
ci-windows
Process completed with exit code 1.
test-integration/apps.test.ts > Nested Middleware > Should apply grandparent middleware to child index route - /without-route/with-index: test-integration/apps.test.ts#L486
AssertionError: expected null to deeply equal 'true' - Expected: "true" + Received: null ❯ test-integration/apps.test.ts:486:63
ci
Failed to restore: Cache service responded with 400
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