Skip to content

refactor: Bump lint-staged from 16.1.0 to 16.2.7#10295

Closed
mtrezza wants to merge 1 commit intoparse-community:alphafrom
mtrezza:chore/deps/lint-staged-16.2.7
Closed

refactor: Bump lint-staged from 16.1.0 to 16.2.7#10295
mtrezza wants to merge 1 commit intoparse-community:alphafrom
mtrezza:chore/deps/lint-staged-16.2.7

Conversation

@mtrezza
Copy link
Copy Markdown
Member

@mtrezza mtrezza commented Mar 24, 2026

Closes #10060

Changes

  • 16.1.1: Fixed function tasks receiving wrong files; fixed --no-stash committing unstaged changes
  • 16.1.2: Fixed deleted files causing git add fatal errors
  • 16.1.3: Added types field to package.json for TypeScript detection
  • 16.1.4: Additional types field for NPM TypeScript detection
  • 16.1.5: Correct git top-level directory detection in worktrees
  • 16.1.6: Improved subprocess termination using SIGKILL
  • 16.2.0: Added --fail-on-changes, --continue-on-error, --hide-unstaged options; removed debug, chalk, lilconfig dependencies for supply-chain hardening
  • 16.2.1: Config file search fix in monorepo subdirectories; restored caret semver ranges
  • 16.2.2: Backup stash handling improvements with --fail-on-changes
  • 16.2.3: --fail-on-changes no longer counts hidden unstaged changes as failures
  • 16.2.4: Updated nano-spawn to v2.0.0; lazy-load YAML dependency
  • 16.2.5: Fixed unhandled promise rejection when task spawning fails; backup stash restored properly
  • 16.2.6: Fixed --continue-on-error where tasks were incorrectly killed with SIGINT
  • 16.2.7: Fixed misleading "failed to spawn" error message for normal task failures

Summary by CodeRabbit

  • Chores
    • Updated development tooling dependencies to latest versions.

@parse-github-assistant
Copy link
Copy Markdown

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

  • Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
  • Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
  • Group code into logical blocks. Add a short comment before each block to explain its purpose.
  • We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
  • Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
  • Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

@parseplatformorg
Copy link
Copy Markdown
Contributor

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 24, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 21a0c9ef-5e45-460c-bd2b-cb6aa4bb6f1c

📥 Commits

Reviewing files that changed from the base of the PR and between cb78133 and de42f4e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

📝 Walkthrough

Walkthrough

The lint-staged development dependency in package.json has been updated from version 16.1.0 to 16.2.7. This incorporates upstream patch fixes addressing spawn failure messaging, termination behavior, promise rejection handling, stash management, and internal dependency updates.

Changes

Cohort / File(s) Summary
Dependency Updates
package.json
Updated lint-staged from 16.1.0 to 16.2.7 to incorporate upstream patch fixes for task spawning, error handling, and stash restoration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mtrezza mtrezza closed this Mar 24, 2026
@mtrezza mtrezza deleted the chore/deps/lint-staged-16.2.7 branch March 24, 2026 01:49
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.54%. Comparing base (b344927) to head (de42f4e).
⚠️ Report is 1 commits behind head on alpha.

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha   #10295      +/-   ##
==========================================
+ Coverage   92.52%   92.54%   +0.01%     
==========================================
  Files         192      192              
  Lines       16502    16502              
  Branches      227      227              
==========================================
+ Hits        15269    15272       +3     
+ Misses       1213     1210       -3     
  Partials       20       20              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants