Update dependency @storybook/testing-library to v0.2.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@storybook/testing-library	0.2.0 → 0.2.2

---

Release Notes

storybookjs/testing-library (@​storybook/testing-library)

v0.2.2

Compare Source

🐛 Bug Fix

• Revert: Temporarily fix user-event to 14.4.0 to avoid compatibility issues #​57 (@​yannbf)

Authors: 1

• Yann Braga (@​yannbf)

v0.2.1

Compare Source

🎉 This release contains work from a new contributor! 🎉

Thank you, Valentin Palkovic (@​valentinpalkovic), for all your work!

🐛 Bug Fix

• Temporarily fix user-event to 14.4.0 to avoid compatibility issues #​53 (@​yannbf)

Authors: 2

• Valentin Palkovic (@​valentinpalkovic)
• Yann Braga (@​yannbf)

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

[augmentcode]

🤖 Augment PR Summary

Summary: Updates Storybook test utilities by bumping @storybook/testing-library from 0.2.0 to 0.2.2.

Changes:

• Refreshes the Storybook workspace lockfile to reflect the dependency bump (includes upstream bugfix around user-event compatibility)

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

Updates Storybook dependency lockfile to align @storybook/testing-library and @testing-library/user-event versions.

• Bumps @storybook/testing-library from 0.2.0 → 0.2.1
• Narrows @testing-library/user-event version range from ^14.0.0 to ~14.4.0, pinning to patch-level updates within 14.4.x
• Resolved @testing-library/user-event version updated to 14.4.3
• Checksums in storybook/yarn.lock updated to reflect new resolved packages

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR is a straightforward dependency version bump in storybook/yarn.lock, updating @storybook/testing-library from 0.2.0 to 0.2.1 and pinning @testing-library/user-event to ~14.4.0 (resolving to 14.4.3). The change is purely a lockfile update with no application logic, no production code paths, and no behavioral changes beyond aligning test tooling versions. The narrowing of the user-event version range from ^14.0.0 to ~14.4.0 is a conservative and deliberate alignment that reduces version drift risk in the Storybook testing environment.

Key Findings:

• The storybook/yarn.lock changes are limited to checksum and resolved-version updates for @storybook/testing-library and @testing-library/user-event, with no production or runtime code modified.
• Pinning @testing-library/user-event to ~14.4.0 (patch-level) instead of the broader ^14.0.0 (minor-level) reduces the risk of unexpected behavior changes from future minor version upgrades in the Storybook testing context.
• No review comments, no heuristic issues, and no unresolved pre-existing concerns were identified — the PR scope is well-contained and the change is low-risk.

Files requiring special attention

• storybook/yarn.lock

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​docusaurus/​module-type-aliases@​0.0.0-5591
	@​docusaurus/​preset-classic@​0.0.0-5591
	@​spotify/​prettier-config@​14.1.3
	@​docusaurus/​plugin-client-redirects@​0.0.0-5591
	@​docusaurus/​core@​0.0.0-5591
	@​types/​webpack-env@​1.18.0 ⏵ 1.18.1
	@​tsconfig/​docusaurus@​1.0.7
	@​types/​luxon@​3.3.0
	docusaurus-plugin-sass@​0.2.4
	clsx@​1.2.1
	js-yaml@​4.1.0
	luxon@​3.3.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm argparse under Python-2.0.1 License: Python-2.0.1 - The applicable license policy does not permit this license (5) (package/LICENSE) From: ? → npm/js-yaml@4.1.0 → npm/argparse@2.0.1 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/argparse@2.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/caniuse-lite@1.0.30001481 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001481. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/entities@4.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report