[PR #504] [MERGED] chore(deps-dev): bump lint-staged from 15.2.7 to 15.2.9 in /web #515

Closed
opened 2026-03-03 16:38:45 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/NdoleStudio/httpsms/pull/504
Author: @dependabot[bot]
Created: 9/1/2024
Status: Merged
Merged: 9/2/2024
Merged by: @AchoArnold

Base: mainHead: dependabot/npm_and_yarn/web/lint-staged-15.2.9


📝 Commits (1)

  • f3fb7e9 chore(deps-dev): bump lint-staged from 15.2.7 to 15.2.9 in /web

📊 Changes

2 files changed (+75 additions, -48 deletions)

View changed files

📝 web/package.json (+1 -1)
📝 web/pnpm-lock.yaml (+74 -47)

📄 Description

Bumps lint-staged from 15.2.7 to 15.2.9.

Release notes

Sourced from lint-staged's releases.

v15.2.9

Patch Changes

  • #1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Patch Changes

  • f0480f0 Thanks @​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.

Changelog

Sourced from lint-staged's changelog.

15.2.9

Patch Changes

  • #1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

15.2.8

Patch Changes

  • f0480f0 Thanks @​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.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/NdoleStudio/httpsms/pull/504 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 9/1/2024 **Status:** ✅ Merged **Merged:** 9/2/2024 **Merged by:** [@AchoArnold](https://github.com/AchoArnold) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/web/lint-staged-15.2.9` --- ### 📝 Commits (1) - [`f3fb7e9`](https://github.com/NdoleStudio/httpsms/commit/f3fb7e95bc9b814aadf65c673ce0cd9fbb9e367b) chore(deps-dev): bump lint-staged from 15.2.7 to 15.2.9 in /web ### 📊 Changes **2 files changed** (+75 additions, -48 deletions) <details> <summary>View changed files</summary> 📝 `web/package.json` (+1 -1) 📝 `web/pnpm-lock.yaml` (+74 -47) </details> ### 📄 Description Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 15.2.7 to 15.2.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lint-staged/lint-staged/releases">lint-staged's releases</a>.</em></p> <blockquote> <h2>v15.2.9</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1463">#1463</a> <a href="https://github.com/lint-staged/lint-staged/commit/b69ce2ddfd5a7ae576f4fef4afc60b8a81f3c945"><code>b69ce2d</code></a> Thanks <a href="https://github.com/iiroj"><code>@​iiroj</code></a>! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning <code>MaxListenersExceededWarning: Possible EventEmitter memory leak detected</code>.</li> </ul> <h2>v15.2.8</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981"><code>f0480f0</code></a> Thanks <a href="https://github.com/iiroj"><code>@​iiroj</code></a>! - In the previous version the native <code>git rev-parse --show-toplevel</code> command was taken into use for resolving the current git repo root. This version switched the <code>--show-toplevel</code> flag with <code>--show-cdup</code>, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js <code>child_process</code>. The new flag returns a path relative to the working directory, avoiding the issue.</p> <p>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.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lint-staged/lint-staged/blob/master/CHANGELOG.md">lint-staged's changelog</a>.</em></p> <blockquote> <h2>15.2.9</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1463">#1463</a> <a href="https://github.com/lint-staged/lint-staged/commit/b69ce2ddfd5a7ae576f4fef4afc60b8a81f3c945"><code>b69ce2d</code></a> Thanks <a href="https://github.com/iiroj"><code>@​iiroj</code></a>! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning <code>MaxListenersExceededWarning: Possible EventEmitter memory leak detected</code>.</li> </ul> <h2>15.2.8</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981"><code>f0480f0</code></a> Thanks <a href="https://github.com/iiroj"><code>@​iiroj</code></a>! - In the previous version the native <code>git rev-parse --show-toplevel</code> command was taken into use for resolving the current git repo root. This version switched the <code>--show-toplevel</code> flag with <code>--show-cdup</code>, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js <code>child_process</code>. The new flag returns a path relative to the working directory, avoiding the issue.</p> <p>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.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lint-staged/lint-staged/commit/0ce5e1455e28d3376cb13de98b1023af1e60942b"><code>0ce5e14</code></a> chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1465">#1465</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/b69ce2ddfd5a7ae576f4fef4afc60b8a81f3c945"><code>b69ce2d</code></a> fix: set max event listeners to the number of tasks (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1463">#1463</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/52f6eef9868ccf291b2e81935a25d5b07c10b5a4"><code>52f6eef</code></a> chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1462">#1462</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/8d8fe23e157f83d846ed9a06bc7c80cfebe0c706"><code>8d8fe23</code></a> build: update repository url in package.json</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981"><code>f0480f0</code></a> Revert &quot;chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1461">#1461</a>)&quot;</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/1da81c0995e2247bf9224f440bf3f40479be40b8"><code>1da81c0</code></a> chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1461">#1461</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/cc04e0802dffda3d74657b3638b0991ee3245856"><code>cc04e08</code></a> ci: add required permission for provenance generation</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/fa2dac862670439049b4f9fe277e05ccaac1d16e"><code>fa2dac8</code></a> Revert &quot;chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1455">#1455</a>)&quot;</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/832598584a22e025eb5721e010f22b9dcf7b4931"><code>8325985</code></a> chore(changeset): release (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1455">#1455</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/92f295ffcff8df62f4c15aee8136ed1795b50b40"><code>92f295f</code></a> build(deps): update dependencies (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1460">#1460</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lint-staged/lint-staged/compare/v15.2.7...v15.2.9">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lint-staged&package-manager=npm_and_yarn&previous-version=15.2.7&new-version=15.2.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-03 16:38:45 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/httpsms#515
No description provided.