chore(deps): update dependency qs to v6.15.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
qs	resolutions	patch	6.15.0 → 6.15.1

---

Release Notes

ljharb/qs (qs)

v6.15.1

Compare Source

• [Fix] parse: parameterLimit: Infinity with throwOnLimitExceeded: true silently drops all parameters
• [Deps] update @ljharb/eslint-config
• [Dev Deps] update @ljharb/eslint-config, iconv-lite
• [Tests] increase coverage

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

This is a routine Renovate bot dependency update for the qs npm package (used in the docs site) from 6.15.0 to 6.15.1. The change is limited to docs/package.json and docs/yarn.lock — no production .NET code is touched.

What changed in qs 6.15.1

The upstream changelog lists one behavioural fix: when parameterLimit is set to Infinity and throwOnLimitExceeded is true, all parameters were silently dropped instead of being preserved. The rest of the release is eslint-config bumps and test coverage increases with no API or security changes.

Assessment

• The scope is correct: only the resolutions pin in package.json and the corresponding lockfile entry are updated.
• The lockfile hash change (db8fd5d... → bdb55ae...) is consistent with a legitimate upstream patch release.
• qs is listed under resolutions (a Yarn override) rather than as a direct dependency. This means it is a transitive dependency being pinned for security/correctness reasons, which is the right practice.
• Auto-merge is already enabled, which is appropriate for a patch-level lockfile-only update to a docs-only dependency.

One minor observation

The qs@~6.14.0 alias in the lockfile is preserved alongside qs@6.15.1 in the same entry. This is expected Yarn behaviour — the ~6.14.0 range is satisfied by 6.15.1 — but it is worth being aware that if any transitive package ever requires a version outside that range, this resolution override will silently shadow it. That is pre-existing behaviour and not introduced by this PR.

No blocking issues. This is safe to merge.