changeset-bot[bot]
commented
4 months ago ⚠️ No Changeset found
Latest commit: 6a387c5c61f81fddea19297d22dada8607b1f7b4
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver typesClick here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
github-actions[bot]
This PR contains the following updates:
15.2.5->15.2.8Release 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. ### [`v15.2.7`](https://togithub.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md#1527) [Compare Source](https://togithub.com/lint-staged/lint-staged/compare/v15.2.6...v15.2.7) ##### Patch Changes - [#1440](https://togithub.com/lint-staged/lint-staged/pull/1440) [`a51be80`](https://togithub.com/lint-staged/lint-staged/commit/a51be804b63307ac7af3c82f4cb2d43dbe92daac) 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 drops the `--path-format=absolute` option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading `git` to the latest version. ### [`v15.2.6`](https://togithub.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md#1526) [Compare Source](https://togithub.com/lint-staged/lint-staged/compare/v15.2.5...v15.2.6) ##### Patch Changes - [#1433](https://togithub.com/lint-staged/lint-staged/pull/1433) [`119adb2`](https://togithub.com/lint-staged/lint-staged/commit/119adb29854cabddbfcf0469d7c8a0126184a5d4) Thanks [@iiroj](https://togithub.com/iiroj)! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.Configuration
📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), 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.