Skip to content

chore(deps-dev): bump lint-staged from 16.1.2 to 17.0.7 - #8

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/lint-staged-17.0.7
Closed

chore(deps-dev): bump lint-staged from 16.1.2 to 17.0.7#8
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/lint-staged-17.0.7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 4, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps lint-staged from 16.1.2 to 17.0.7.

Release notes

Sourced from lint-staged's releases.

v17.0.7

Patch Changes

v17.0.6

Patch Changes

  • #1803 bdf2770 - Run all tests with Deno, in addition to Node.js and Bun.

  • #1796 7508272 - Fix performance regression of lint-staged v17 by going back to using git add to stage task modifications. This was changed to git update-index --again in v17 for less manual work, but unfortunately the update-index command gets slower in very large Git repos.

  • #1797 7b2505a - This version of lint-staged uses the new staged publishing for npm packages feature. Releases are already published from GitHub Actions with trusted publishing, but now an additional approval with two-factor authentication is also required.

  • #1802 321b0a9 - Downgrade dependency tinyexec@1.2.2 to avoid issues in version 1.2.3.

v17.0.5

Patch Changes

  • #1792 1f67271 - Correctly set the --max-arg-length default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.

v17.0.4

Patch Changes

  • #1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Patch Changes

  • #1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

v17.0.2

Patch Changes

v17.0.1

Patch Changes

  • #1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.0.7

Patch Changes

17.0.6

Patch Changes

  • #1803 bdf2770 - Run all tests with Deno, in addition to Node.js and Bun.

  • #1796 7508272 - Fix performance regression of lint-staged v17 by going back to using git add to stage task modifications. This was changed to git update-index --again in v17 for less manual work, but unfortunately the update-index command gets slower in very large Git repos.

  • #1797 7b2505a - This version of lint-staged uses the new staged publishing for npm packages feature. Releases are already published from GitHub Actions with trusted publishing, but now an additional approval with two-factor authentication is also required.

  • #1802 321b0a9 - Downgrade dependency tinyexec@1.2.2 to avoid issues in version 1.2.3.

17.0.5

Patch Changes

  • #1792 1f67271 - Correctly set the --max-arg-length default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.

17.0.4

Patch Changes

  • #1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

17.0.3

Patch Changes

  • #1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

17.0.2

Patch Changes

17.0.1

... (truncated)

Commits
  • cd11fec Merge pull request #1807 from lint-staged/changeset-release/main
  • 15a8ee0 chore(changeset): release
  • 797bbd9 Merge pull request #1808 from lint-staged/add-stashing-faq
  • 504e307 docs: add FAQ entry on how stashing works
  • eff5cd1 Merge pull request #1806 from lint-staged/update-tinyexec
  • e692e58 build(deps): update tinyexec@^1.2.4
  • a2dd4ea Merge pull request #1805 from lint-staged/update-github-templates
  • c928519 docs: update GitHub templates
  • 094ba56 Merge pull request #1798 from lint-staged/changeset-release/main
  • 88e19fe chore(changeset): release
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for lint-staged since your current version.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 4, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lint-staged-17.0.7 branch 3 times, most recently from ca69d0b to 9746021 Compare June 7, 2026 05:46
@dependabot
chore(deps-dev): bump lint-staged from 16.1.2 to 17.0.7
29d0959 
Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 16.1.2 to 17.0.7.
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v16.1.2...v17.0.7)

---
updated-dependencies:
- dependency-name: lint-staged
  dependency-version: 17.0.7
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lint-staged-17.0.7 branch from 9746021 to 29d0959 Compare June 7, 2026 16:47
@alsterg alsterg closed this Jun 9, 2026
@alsterg
alsterg deleted the dependabot/npm_and_yarn/lint-staged-17.0.7 branch June 9, 2026 14:17
@dependabot @github

dependabot Bot commented on behalf of github Jun 9, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

alsterg added a commit that referenced this pull request Jun 10, 2026
@alsterg
feat(cli): add ExtensionHost ask dispatcher control and session-resum…
cbeacad 
…e bootstrap

Add public methods to ExtensionHost for controlling the AskDispatcher:
- grantResume(): grant one auto-resume credit (already used by resumeTask)
- setAskDispatcherEnabled(enabled): enable/disable ask auto-handling

Add AskDispatcher.setDisabled() for runtime toggle of ask handling.

Rework bootstrapResumeForStdinStream() to suppress the AskDispatcher
before showTaskWithId so the resume_completed_task ask stays pending
for the subsequent stdin "message" command to answer. Uses a two-phase
wait: event-driven TaskStarted + polling hasActiveTask&&isWaitingForInput.

This is infrastructure toward fixing test #8 (session-resume) from
todos/fixing_tests.md.
alsterg added a commit that referenced this pull request Jun 11, 2026
@alsterg
docs: remove fetch_web_page from unconditional auto-approval document…
05b9ef7 
…ation

Reflect that fetch_web_page is no longer unconditionally auto-approved.
It now falls through to the read-group gating path (alwaysAllowReadOnly toggle).

- auto_approval.md: removed from unconditional table and alwaysAllowReadOnly
  table; updated example in ALWAYS_AVAILABLE_TOOLS vs Auto-Approval section
  and reviewer note #8
- terminology.md: removed fetchWebPage from 'unconditionally auto-approved
  tool' definition
- adding-new-tools.md: changed example from fetchWebPage to findFiles
- integration-tests/auto-approval.test-scenarios.yaml: removed fetchWebPage
  from 'lightweight read-only tools unconditionally approved' test case

Note: lint failure in webview-ui/src/hooks/useScrollLifecycle.ts is from
a parallel session external change.
alsterg added a commit that referenced this pull request Jun 13, 2026
@alsterg
docs(git_search): architecture diagram still called GitWatcher a Phas…
d70a01f 
…e-1 stub

GitWatcher is a real ~199-line Phase-2 implementation (setInterval polling
via 'git log --since=<lastCommitDate>'), but the architecture tree still
labelled it 'stub in Phase 1'. Updated the diagram and marked the doc's own
gap #8 resolved.
alsterg added a commit that referenced this pull request Jul 7, 2026
@alsterg
feat(plugins): P2.5 wire code-plugin activation + per-hook 500ms timeout
b8038b2 
PluginManager.activateCodePlugins loads each enabled code plugin via the loader,
wraps it so its hooks receive a per-plugin PluginContext (resolved config +
restricted sandbox host injected via closure), and registers it into
pluginRegistry. Idempotent + reconciling: unregisters disabled/failed-closed
plugins; load failures are warned + isolated. ShoferProvider constructs the
manager with the node code loader + host + pluginConfigs and kicks off
activateCodePlugins non-blocking (owner #8). Add PLUGIN_HOOK_TIMEOUT_MS guard
around collectTools/transformSystemPrompt and a registry.unregister/has. Extract
warnPlugin/warnPluginConflict to plugin-warnings.ts to avoid an import cycle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@alsterg