Skip to content

fix: use custom mtime for last-modified if available #290

fix: use custom mtime for last-modified if available

fix: use custom mtime for last-modified if available #290

Triggered via pull request November 8, 2024 13:24
Status Success
Total duration 22s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 warnings and 2 notices
Unit Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Unit Tests
Total Tests: 20 Suites 📂: 3 Passed ✅: 20 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 356.364ms
E2E Tests
Total Tests: 20 Suites 📂: 3 Passed ✅: 20 Failed ❌: 0 Canceled 🚫: 0 Skipped ⏭️: 0 Todo 📝: 0 Duration 🕐: 1747.716ms