fix(ci): lock foundry version

[kaze-cow]

now that foundry has stable releases, there is no reason to subject ourselves to the instability of the nightly releases. this PR proposes locking to the current foundry release v1.3.5, and we can manually bump it as it makes sense.

as it so happens, the current nightly release seems to be changing the lint rules or something and the CI is currently failing with main branch code.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nomicfoundation/​solidity-analyzer-darwin-arm64@​0.1.1
	@​nomicfoundation/​solidity-analyzer-darwin-x64@​0.1.1
	@​nomicfoundation/​solidity-analyzer-freebsd-x64@​0.1.1
	@​nomicfoundation/​solidity-analyzer-linux-arm64-gnu@​0.1.1
	@​nomicfoundation/​solidity-analyzer-linux-arm64-musl@​0.1.1
	@​nomicfoundation/​solidity-analyzer-linux-x64-gnu@​0.1.1
	@​nomicfoundation/​solidity-analyzer-linux-x64-musl@​0.1.1
	@​nomicfoundation/​solidity-analyzer-win32-arm64-msvc@​0.1.1
	@​nomicfoundation/​solidity-analyzer-win32-ia32-msvc@​0.1.1
	@​nomicfoundation/​solidity-analyzer-win32-x64-msvc@​0.1.1
	is-unicode-supported@​0.1.0
	aggregate-error@​3.1.0
	indent-string@​4.0.0
	babel-helper-optimise-call-expression@​6.24.1
	babel-helper-get-function-arity@​6.24.1
	is-arrayish@​0.2.1
	ghost-testrpc@​0.0.2
	charenc@​0.0.2
	get-value@​2.0.6
	babel-helper-regex@​6.26.0
	home-or-tmp@​2.0.0
	is-finite@​1.1.0
	copy-descriptor@​0.1.1
	babel-helper-builder-binary-assignment-operator-visitor@​6.24.1
	has-ansi@​2.0.0
	crypt@​0.0.2
	babel-helper-call-delegate@​6.24.1
	babel-helper-hoist-variables@​6.24.1
	babel-helper-explode-assignable-expression@​6.24.1
	@​pnpm/​network.ca-file@​1.0.2
	babel-helper-function-name@​6.24.1
	@​pnpm/​config.env-replace@​1.1.0
	@​types/​concat-stream@​1.6.0
See 135 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		[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: >= 0 Patched version: No patched versions From: yarn.lock → npm/[email protected] → npm/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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		[email protected] has a Critical CVE. CVE: GHSA-2j2x-2gpw-g8fm flat vulnerable to Prototype Pollution (CRITICAL) Affected versions: < 5.0.1 Patched version: 5.0.1 From: yarn.lock → npm/[email protected] → npm/[email protected] ℹ 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 [email protected]. 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/[email protected]. 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

[anxolin]

👍