chore: upgrade dependencies with yarn upgrade-interactive

[rap2hpoutre]

Je fais un tour sur l'update des dépendances "sans risques" (celles qui sont marquées en vert ou jaune par yarn upgrade-interactive) pour diminuer l'importance de la PR #522 (on va voir si ça marche 😬)

[revu-bot]

An error occurred: 400 {"type":"error","error":{"type":"invalid_request_error","message":"prompt is too long: 223545 tokens > 200000 maximum"},"request_id":"req_011CTsWaxGHoRv5QsG2raEsG"}

Revu logs

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	form-data@​3.0.4 ⏵ 4.0.3	+1	-75
	@​sentry/​cli-darwin@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-linux-arm@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-linux-arm64@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-linux-i686@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-linux-x64@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-win32-arm64@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-win32-i686@​2.53.0 ⏵ 2.55.0
	@​sentry/​cli-win32-x64@​2.53.0 ⏵ 2.55.0
	array-flatten@​1.1.1
	@​prisma/​engines-version@​4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
	side-channel@​1.1.0
	minimalistic-assert@​1.0.1
	is-arrayish@​0.3.2 ⏵ 0.2.1	+1
	unique-slug@​4.0.0 ⏵ 5.0.0
	@​jest/​globals@​29.7.0
	@​jest/​get-type@​30.1.0
	@​jest/​source-map@​29.6.3
	unique-filename@​3.0.0 ⏵ 4.0.0
	ignore-by-default@​1.0.1
	@​svgr/​babel-plugin-remove-jsx-empty-expression@​8.0.0
	jest-resolve-dependencies@​29.7.0
	@​jest/​expect@​29.7.0
	@​types/​mime@​1.3.5
	@​jest/​test-sequencer@​29.7.0
	chownr@​2.0.0 ⏵ 3.0.0			+1
	collect-v8-coverage@​1.0.2
	@​jest/​test-result@​29.7.0
	@​slack/​types@​1.10.0
	jest@​29.7.0
	@​jest/​console@​29.7.0
	escape-string-regexp@​4.0.0 ⏵ 2.0.0			-2
	dezalgo@​1.0.4
See 275 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		form-data@2.3.3 has a Critical CVE. CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 2.5.4 From: ? → npm/node-talisman@1.29.22 → npm/form-data@2.3.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/form-data@2.3.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		form-data@4.0.3 has a Critical CVE. CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 4.0.4 From: app/yarn.lock → npm/form-data@4.0.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/form-data@4.0.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		safer-buffer@2.1.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/node-talisman@1.29.22 → npm/safer-buffer@2.1.2 ℹ 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/safer-buffer@2.1.2. 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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tokenbureau]

🎉 This PR is included in version 1.98.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀