typicode/husky (husky)
### [`v9.1.4`](https://togithub.com/typicode/husky/compare/v9.1.3...fc549e0e5c8723a6d796f6ad26ef6590769f5d82)
[Compare Source](https://togithub.com/typicode/husky/compare/v9.1.3...v9.1.4)
davidparsson/junit-report-builder (junit-report-builder)
### [`v4.0.1`](https://togithub.com/davidparsson/junit-report-builder/compare/4.0.0...4.0.1)
[Compare Source](https://togithub.com/davidparsson/junit-report-builder/compare/4.0.0...4.0.1)
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 - "after 2pm on Saturday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
9.1.3
->9.1.4
4.0.0
->4.0.1
15.2.7
->15.2.8
Release Notes
typicode/husky (husky)
### [`v9.1.4`](https://togithub.com/typicode/husky/compare/v9.1.3...fc549e0e5c8723a6d796f6ad26ef6590769f5d82) [Compare Source](https://togithub.com/typicode/husky/compare/v9.1.3...v9.1.4)davidparsson/junit-report-builder (junit-report-builder)
### [`v4.0.1`](https://togithub.com/davidparsson/junit-report-builder/compare/4.0.0...4.0.1) [Compare Source](https://togithub.com/davidparsson/junit-report-builder/compare/4.0.0...4.0.1)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 - "after 2pm on Saturday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.