root/dvf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

renovate #55

Merged
root merged 1 commits from renovate into master 2025-09-23 03:35:59 +00:00
Conversation 0 Commits 1 Files Changed 2 +15 -69
m.schnitzler commented 2025-09-23 03:19:48 +00:00
Contributor
Copy Link

npm

lint-staged

  • ^16.1.6 => ^16.2.0 (dvf)

Minor Changes

  • #1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made by tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.

  • #1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.

  • #1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.

  • #1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at https://github.com/debug-js/debug/issues/1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging

  • #1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

    Thanks to @ItsNickBarry for the idea and initial implementation in #1552.

  • #1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

<h1>npm</h1> <h2>lint-staged</h2> <ul> <li> ^16.1.6 => ^16.2.0 (dvf)</li> </ul> > <h3>Minor Changes</h3> > <ul> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1615">#1615</a> <a href="https://github.com/lint-staged/lint-staged/commit/99eb74200e8db69e72dba45314025953b8b0794e"><code>99eb742</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Added a new option <code>--fail-on-changes</code> to make <em>lint-staged</em> exit with code 1 when tasks modify any files, making the <code>precommit</code> hook fail. This is similar to the <code>git diff --exit-code</code> option. Using this flag also implies the <code>--no-revert</code> flag which means any changes made by tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1611">#1611</a> <a href="https://github.com/lint-staged/lint-staged/commit/cd05fd349594baf586fbafb05588ff07d86060b7"><code>cd05fd3</code></a> Thanks <a href="https://github.com/rlorenzo">@rlorenzo</a>! - Added a new option <code>--continue-on-error</code> so that <em>lint-staged</em> will run all tasks to completion even if some of them fail. By default, <em>lint-staded</em> will exit early on the first failure.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1637">#1637</a> <a href="https://github.com/lint-staged/lint-staged/commit/82fcc0789c17bf6b2ea2649147abec77fa619375"><code>82fcc07</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Internal <em>lint-staged</em> errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there&#39;s a syntax error in the <em>lint-staged</em> configuration file.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1647">#1647</a> <a href="https://github.com/lint-staged/lint-staged/commit/a5ecc0605d52756167417c84cb0007ea7bceaaa3"><code>a5ecc06</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Remove <a href="https://github.com/debug-js/debug">debug</a> as a dependency due to recent malware issue; read more at <a href="https://github.com/debug-js/debug/issues/1005">https://github.com/debug-js/debug/issues/1005</a>. Because of this, the <code>DEBUG</code> environment variable is no longer supported — use the <code>--debug</code> to enable debugging</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1636">#1636</a> <a href="https://github.com/lint-staged/lint-staged/commit/8db2717574ebfa2b80e0fc4eb0b24d705fd264fc"><code>8db2717</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Added a new option <code>--hide-unstaged</code> so that <em>lint-staged</em> will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags <code>--hide-unstaged --no-hide-partially-staged</code> isn&#39;t meaningful and behaves the same as just <code>--hide-unstaged</code>.</p> > <p>Thanks to <a href="https://github.com/ItsNickBarry">@ItsNickBarry</a> for the idea and initial implementation in <a href="https://github.com/lint-staged/lint-staged/pull/1552">#1552</a>.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1648">#1648</a> <a href="https://github.com/lint-staged/lint-staged/commit/7900b3b79c5e2e69662cb8b1bcbcae79c3549421"><code>7900b3b</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Remove <a href="https://github.com/antonk52/lilconfig">lilconfig</a> to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into <em>lint-staged</em> and should work about the same.</p> > </li> > </ul> > <h3>Patch Changes</h3> > <ul> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1633">#1633</a> <a href="https://github.com/lint-staged/lint-staged/commit/7f9e485a981707897e0d417f6a62008f0c098e00"><code>7f9e485</code></a> Thanks <a href="https://github.com/apps/dependabot">@dependabot</a>! - Bumps <a href="https://github.com/listr2/listr2">listr2</a> from 9.0.3 to 9.0.4.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1626">#1626</a> <a href="https://github.com/lint-staged/lint-staged/commit/99d5a9b0ddcba7d471d39ff3969d37988f1e2705"><code>99d5a9b</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Due to recent phishing attacks, for example <a href="https://github.com/chalk/chalk/issues/656">chalk@5.6.1</a> was released with malware. To avoid <em>lint-staged</em>&#39;s users being at risk the <strong>direct dependencies are pinned to exact versions</strong>, instead of allowing future patch versions with the <a href="https://docs.npmjs.com/cli/v6/using-npm/semver#caret-ranges-123-025-004">caret (<code>^</code>) range</a>.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1588">#1588</a> <a href="https://github.com/lint-staged/lint-staged/commit/035bbf268ac47bbaf2cfa737c3b2240d38feb22e"><code>035bbf2</code></a> Thanks <a href="https://github.com/outslept">@outslept</a>! - Increase performance by listing staged files and searching for configuration concurrently.</p> > </li> > <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1645">#1645</a> <a href="https://github.com/lint-staged/lint-staged/commit/deba3ad83581938dd71b86b563e62827b5fc2a0a"><code>deba3ad</code></a> Thanks <a href="https://github.com/iiroj">@iiroj</a>! - Remove <a href="https://github.com/chalk/chalk">chalk</a> as a dependency due to recent malware issue; read more at <a href="https://github.com/chalk/chalk/issues/656">https://github.com/chalk/chalk/issues/656</a>.</p> > <p>If you are having trouble with ANSI color codes when using <em>lint-staged</em>, you can try setting either <code>FORCE_COLOR=true</code> or <code>NO_COLOR=true</code> env variables.</p> > </li> > </ul>
m.schnitzler added 1 commit 2025-09-23 03:19:51 +00:00
fix: "renovate" 6fa860f1fe
root merged commit 5523f11320 into master 2025-09-23 03:35:58 +00:00
root referenced this issue from a commit 2025-09-23 03:36:01 +00:00
renovate (#55)
root deleted branch renovate 2025-09-23 03:36:10 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
root
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: root/dvf#55
No description provided.
Delete Branch "renovate"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?