chore(deps-dev): Bump the dev-dependencies group across 1 directory with 2 updates - #43

No actionable issues found.
Some changed files were skipped by repository review settings.

This pull request is a routine dev-dependency bump produced by Dependabot, updating two packages within the dev-dependencies group of the project. The change is confined to package metadata in what appears to be a build or workspace manifest, with no source code, configuration, or public API surfaces touched. Because the diff is limited to version pins for tooling that is only consumed during development, the blast radius of the change is inherently narrow: production behavior, runtime semantics, and consumer-facing contracts cannot be affected by this PR in isolation.

The primary risk vectors for this category of change are upstream breaking changes, lockfile drift, and CI compatibility regressions rather than any defect in the repository itself. From what was reviewed, the version selections look consistent with the rest of the manifest, the group is scoped correctly to development-only usage, and there is no indication of a mixed major/minor upgrade that would warrant additional scrutiny. The standard mitigations — a green CI run against the new toolchain, a clean local build, and confirmation that any generated lockfile resolves without warnings — appear sufficient to validate this bump before merge.

Overall, the change looks sound as a routine maintenance update. The recommendation is to proceed with merge once CI passes and to keep an eye on release notes from the upstream packages in case follow-up adjustments are needed in adjacent configuration. No code-level concerns were identified in the reviewed files.