Bump lint-staged from 17.5.0 to 17.5.1

[dependabot]

Bumps lint-staged from 17.5.0 to 17.5.1.

Release notes

Sourced from lint-staged's releases.

v17.5.1

Patch Changes

• #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

  A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

Changelog

Sourced from lint-staged's changelog.

17.5.1

Patch Changes

• #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

  A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

Commits

• f8b1ab1 Merge pull request #1853 from lint-staged/changeset-release/main
• 3b54961 chore(changeset): release
• 09317ff Merge pull request #1852 from lint-staged/fix-ambient-declaration
• bfcca94 fix: change defineConfig signature from const to a function
• See full diff in compare view

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 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)

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, including the package name and old → new version, then check where that dependency is actually used in the codebase, or whether it is unused, and summarize the potential impact.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — Add a changelog entry only for changes that an Azurite user, operator, SDK developer, or extension user could reasonably observe. Exclude internal maintenance, testing, CI/CD, linting, and development dependency updates unless they result in a user-visible behaviour, compatibility, performance, or security improvement.
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — your final response must use the following structure exactly (no free-form paragraph summary).

Impact analysis

• Package:
• Old version:
• New version:
• Change Impact:

Build/Conflict Issues

• Commands:
• Result:

Tests

• Added:
• Updated:
• Result:

Run the Suite

• Commands:
• Status:

Changelog

• Entry:
• Location:

Comments

• Reviewed:
• Actions:

Self-Rate

• Score:
• Reasoning:

Summary

• Why this matters:
• Risk of not taking change:

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, i...

Impact analysis

• Package: lint-staged
• Old version: 17.5.0
• New version: 17.5.1
• Change Impact: Package-lock-only patch update for a direct development dependency. lint-staged is declared in package.json/package-lock.json, has .lintstagedrc config, and is covered by tests/packageScripts.test.ts; no Azurite runtime/service code uses it.

Build/Conflict Issues

• Commands: npm ci --legacy-peer-deps, npm run build, npm run lint; also checked GitHub Actions runs/jobs and failed-job logs.
• Result: All local commands passed. No merge conflicts or lint/build errors found. GitHub Actions CodeQL and Dependabot agent runs were successful; PR validation was still in progress, with no failed jobs when logs were requested.

Tests

• Added: None.
• Updated: None.
• Result: No new dependency-only tests were added because the change does not alter Azurite behavior; existing package-script coverage already validates the lint-staged config shape.

Run the Suite

• Commands: npm run test:package-scripts; also verified npx lint-staged --version reports 17.5.1.
• Status: Passed, 8 tests passing.

Changelog

• Entry: None.
• Location: Not applicable; this is an internal development dependency patch update with no user-visible Azurite behavior, compatibility, performance, or security change.

Comments

• Reviewed: PR comments and review threads for Bump lint-staged from 17.5.0 to 17.5.1 #2806; review threads returned 0 and the only actionable PR comment was this Copilot request.
• Actions: Addressed by validation and analysis on commit 4b580ef; no file changes were needed.

Self-Rate

• Score: 10/10
• Reasoning: Correctness, build/lint health, targeted test coverage, changelog decision, dependency advisory check, secret scan, and comment review are complete for a package-lock-only development dependency patch.

Summary

• Why this matters: Keeps the locked development tooling patch current while confirming Azurite runtime behavior is unaffected.
• Risk of not taking change: The lockfile would remain on the older lint-staged patch version, missing upstream maintenance fixes for the development workflow.