Closed renovate[bot] closed 2 months ago
✓ no_errors{server:node-http,mode:no-schema}
✓ expected_result{server:node-http,mode:no-schema}
✓ no_errors{server:node-http,mode:json-schema}
✓ expected_result{server:node-http,mode:json-schema}
✓ no_errors{server:uWebSockets,mode:no-schema}
✓ expected_result{server:uWebSockets,mode:no-schema}
✓ no_errors{server:uWebSockets,mode:json-schema}
✓ expected_result{server:uWebSockets,mode:json-schema}
checks......................................: 100.00% ✓ 891696 ✗ 0
data_received...............................: 81 MB 674 kB/s
data_sent...................................: 57 MB 472 kB/s
http_req_blocked............................: avg=1.54µs min=891ns med=1.51µs max=259.56µs p(90)=1.94µs p(95)=2.09µs
http_req_connecting.........................: avg=1ns min=0s med=0s max=125.75µs p(90)=0s p(95)=0s
http_req_duration...........................: avg=190.31µs min=127.61µs med=179.39µs max=8.8ms p(90)=204.4µs p(95)=212.76µs
{ expected_response:true }................: avg=190.31µs min=127.61µs med=179.39µs max=8.8ms p(90)=204.4µs p(95)=212.76µs
✓ { server:node-http,mode:json-schema }.....: avg=203.88µs min=151.81µs med=192.14µs max=7.57ms p(90)=215µs p(95)=222.12µs
✓ { server:node-http,mode:no-schema }.......: avg=194.7µs min=141.08µs med=180.74µs max=8.8ms p(90)=203.96µs p(95)=212.57µs
✓ { server:uWebSockets,mode:json-schema }...: avg=186.04µs min=137.3µs med=176.68µs max=7.36ms p(90)=197.99µs p(95)=204.17µs
✓ { server:uWebSockets,mode:no-schema }.....: avg=178.06µs min=127.61µs med=168.18µs max=8.18ms p(90)=189.79µs p(95)=196.61µs
http_req_failed.............................: 0.00% ✓ 0 ✗ 445848
http_req_receiving..........................: avg=23.28µs min=12.14µs med=22.86µs max=1.39ms p(90)=28.19µs p(95)=30.04µs
http_req_sending............................: avg=8.92µs min=5.41µs med=9.07µs max=334.81µs p(90)=11.77µs p(95)=12.86µs
http_req_tls_handshaking....................: avg=0s min=0s med=0s max=0s p(90)=0s p(95)=0s
http_req_waiting............................: avg=158.1µs min=99.37µs med=147.27µs max=8.74ms p(90)=170.11µs p(95)=178.09µs
http_reqs...................................: 445848 3715.365732/s
iteration_duration..........................: avg=264.36µs min=190.3µs med=252.93µs max=8.93ms p(90)=280.31µs p(95)=290.7µs
iterations..................................: 445848 3715.365732/s
vus.........................................: 1 min=1 max=1
vus_max.....................................: 2 min=2 max=2
This PR contains the following updates:
15.2.7
->15.2.8
Release Notes
lint-staged/lint-staged (lint-staged)
### [`v15.2.8`](https://togithub.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md#1528) [Compare Source](https://togithub.com/lint-staged/lint-staged/compare/v15.2.7...v15.2.8) ##### Patch Changes - [`f0480f0`](https://togithub.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981) Thanks [@iiroj](https://togithub.com/iiroj)! - In the previous version the native `git rev-parse --show-toplevel` command was taken into use for resolving the current git repo root. This version switched the `--show-toplevel` flag with `--show-cdup`, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js `child_process`. The new flag returns a path relative to the working directory, avoiding the issue. The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.