build(deps): bump react from 18.3.0 to 18.3.1 in /client

[dependabot]

Bumps react from 18.3.0 to 18.3.1.

Release notes

Sourced from react's releases.

18.3.1 (April 26, 2024)

• Export act from react f1338f

Changelog

Sourced from react's changelog.

18.3.1 (April 26, 2024)

• Export act from react f1338f

Commits

• f1338f8 Export React.act from 18.3
• d6c42f7 Bump to 18.3.1
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pbkdf2@​3.0.17
	json-schema@​0.4.0 ⏵ 0.2.3	+1	-75	+1
	elliptic@​6.4.1 ⏵ 6.5.3	+1
	original-require@​1.0.1
	number-is-nan@​1.0.1
	is-unicode-supported@​0.1.0
	jsonify@​0.0.1
	isarray@​1.0.0
	path-parse@​1.0.7
	available-typed-arrays@​1.0.7 ⏵ 1.0.5	+1		-3
	is-generator-function@​1.0.10
	is-core-module@​2.13.0
	safe-buffer@​5.2.0
	json-stable-stringify@​1.0.2
	constant-case@​2.0.0
	object-assign@​4.1.1
	is-typed-array@​1.1.12
	@​truffle/​error@​0.2.2
	pinkie-promise@​2.0.1
	camel-case@​4.1.2 ⏵ 3.0.0	+1		-25
	apollo-datasource@​3.3.2
	get-caller-file@​1.0.3
	@​graphql-typed-document-node/​core@​3.2.0
	@​redux-saga/​deferred@​1.2.1
	@​redux-saga/​delay-p@​1.2.1
	@​apollo/​utils.printwithreducedwhitespace@​1.1.0
	@​apollo/​utils.dropunuseddefinitions@​1.1.0
	@​redux-saga/​symbols@​1.1.3
	invert-kv@​1.0.0
	@​apollo/​utils.sortast@​1.1.0
	browserify-sha3@​0.0.4
	@​types/​responselike@​1.0.0
	is-plain-obj@​3.0.0 ⏵ 1.1.0			-13
See 375 more rows in the dashboard

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		json-schema@0.2.3 has a Critical CVE. CVE: GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution (CRITICAL) Affected versions: < 0.4.0 Patched version: 0.4.0 From: package-lock.json → npm/json-schema@0.2.3 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/json-schema@0.2.3. 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		pbkdf2@3.0.17 has a Critical CVE. CVE: GHSA-h7cp-r72f-jxh6 pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos (CRITICAL) Affected versions: >= 3.0.10 < 3.1.3 Patched version: 3.1.3 From: package-lock.json → npm/pbkdf2@3.0.17 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.0.17. 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		pbkdf2@3.0.17 has a Critical CVE. CVE: GHSA-v62p-rq8g-8h59 pbkdf2 silently disregards Uint8Array input, returning static keys (CRITICAL) Affected versions: < 3.1.3 Patched version: 3.1.3 From: package-lock.json → npm/pbkdf2@3.0.17 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/pbkdf2@3.0.17. 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		es5-ext@0.10.63 is Protestware or potentially unwanted behavior. Note: The script attempts to run a local '_postinstall' script, but it does so in a way that suppresses errors. This could potentially hide malicious behavior if '_postinstall' contains harmful code. From: package-lock.json → npm/es5-ext@0.10.63 ℹ Read more on: This package | This alert | What is protestware? 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: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es5-ext@0.10.63. 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

[dependabot]

Superseded by #916.