Update foundry-rs/foundry-toolchain action to v1.5.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
foundry-rs/foundry-toolchain	action	minor	v1.4.0 -> v1.5.0

---

Release Notes

foundry-rs/foundry-toolchain (foundry-rs/foundry-toolchain)

v1.5.0

Compare Source

Features

• chore(ci): bump to node 24 + update dependencies by @​zerosnacks in #​77
• feat(ci): add test matrix for CI workflow, fix docs, fix arch mapping + include arm64 by @​zerosnacks in #​87

Other

• chore: add CODEOWNERS by @​zerosnacks in #​78
• fix: update instructions for PR by @​zerosnacks in #​79
• chore(ci): continue harden, cancel concurrent, revoke unnecessary write by @​zerosnacks in #​81
• chore(ci): add CodeQL by @​zerosnacks in #​82
• chore(ci): rescope permissions according to principle of least privilege by @​zerosnacks in #​83
• chore(ci): add ci-success + merge codeql into regular ci + add dependabot by @​zerosnacks in #​84
• chore(docs): update README by @​zerosnacks in #​88
• chore(deps): bump to 1.5.0, bump @​actions/cache, bump @​vercel/ncc by @​zerosnacks in #​89
• nit(docs): fix default permissions by @​zerosnacks in #​90

Full Changelog: foundry-rs/foundry-toolchain@v1.4.0...v1.5.0

---

Configuration

📅 Schedule: 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 is behind base branch, 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		[email protected] is a AI-detected potential code anomaly. Notes: The code represents a conventional, non-obfuscated part of AJV’s custom keyword support. No direct malicious actions are evident within this module. Security concerns mainly arise from the broader supply chain: the external rule implementation (dotjs/custom), the definition schema, and any user-supplied keyword definitions. The dynamic compilation path (compile(metaSchema, true)) should be exercised with trusted inputs. Recommended follow-up: review the contents of the external modules and monitor the inputs supplied to addKeyword/definitionSchema to ensure no unsafe behavior is introduced during validation or data handling. Confidence: 1.00 Severity: 0.60 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. 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.
Block		[email protected] is a AI-detected potential code anomaly. Notes: No definitive malware detected in this fragment. The main security concern is supply-chain risk from dynamically loading plugins from potentially untrusted sources. To mitigate, enforce strict plugin provenance, disable remote plugin loading, verify plugin integrity, and apply least-privilege execution for plugins. Confidence: 1.00 Severity: 0.60 From: package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. 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.
Block		[email protected] is a AI-detected potential code anomaly. Notes: The code is a conventional, well-scoped implementation of an RxJS-like concat operator. No malicious behavior, data exfiltration, or suspicious I/O detected in this fragment. Security risk is low; malware likelihood is negligible for this isolated operator function. Confidence: 1.00 Severity: 0.60 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. 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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	node-releases@​2.0.19
	indent-string@​5.0.0
	@​changesets/​should-skip-package@​0.1.2
	@​changesets/​changelog-git@​0.2.1
	@​pkgr/​core@​0.2.9
	@​changesets/​get-version-range-type@​0.4.0
	tr46@​0.0.3
	@​changesets/​errors@​0.2.0
	@​changesets/​changelog-github@​0.5.1
	strip-bom@​3.0.0
	better-path-resolve@​1.0.0
	min-indent@​1.0.1
	@​typescript-eslint/​visitor-keys@​8.39.1
	@​typescript-eslint/​parser@​8.39.1
	is-builtin-module@​5.0.0
	@​typescript-eslint/​project-service@​8.39.1
	prettier-linter-helpers@​1.0.0
	read-yaml-file@​1.1.0
	is-subdir@​1.2.0
	@​changesets/​read@​0.6.5
	typescript-eslint@​8.39.1
	@​changesets/​git@​3.0.4
	@​changesets/​get-dependents-graph@​2.1.3
	json-buffer@​3.0.1
	caniuse-lite@​1.0.30001735
	@​changesets/​types@​6.1.0
	@​changesets/​get-release-plan@​4.0.13
	@​types/​json-schema@​7.0.15
	@​types/​estree@​1.0.8
	lodash.startcase@​4.4.0
	update-browserslist-db@​1.1.3
	extendable-error@​0.1.7
	@​manypkg/​find-root@​1.1.0
See 111 more rows in the dashboard

View full report