Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 15 additions & 9 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -96,9 +96,9 @@
"@storybook/addon-docs": "10.5.7",
"@storybook/react-vite": "10.5.7",
"@testing-library/dom": "10.4.1",
"@testing-library/jest-dom": "7.0.0",
"@testing-library/jest-dom": "7.0.1",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 package.json now pins @testing-library/jest-dom at 7.0.1 and @testing-library/user-event at 14.6.4, but package-lock.json still records the old versions (7.0.0 at the root packages[""].devDependencies entry and node_modules/@testing-library/jest-dom, and 14.6.3 for node_modules/@testing-library/user-event). npm ci requires the manifest and lockfile to be in sync, so the CI jobs that run npm ci (e.g. check-ci-validation.yml, chromatic.yml, publish-package-release.yml) will fail on this branch. Regenerate the lockfile with npm install (or npm install --package-lock-only) and commit the updated package-lock.json.

"@testing-library/react": "16.3.2",
"@testing-library/user-event": "14.6.3",
"@testing-library/user-event": "14.6.4",
"@types/classnames": "2.3.4",
"@types/jest": "28.1.8",
"@types/jest-axe": "3.5.9",
Expand Down
Loading