Update dependency @openzeppelin/hardhat-upgrades to v3.2.1

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@openzeppelin/hardhat-upgrades (source)	3.2.0 -> 3.2.1

---

Release Notes

OpenZeppelin/openzeppelin-upgrades (@​openzeppelin/hardhat-upgrades)

### [`v3.2.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/blob/HEAD/packages/plugin-hardhat/CHANGELOG.md#321-2024-07-31) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@3.2.0...@openzeppelin/hardhat-upgrades@3.2.1) - Fix Hardhat compile error when public variables are used to implement interface functions. ([#​1055](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/1055)) - Remove non-struct NatSpec from Hardhat compilation step for namespaced storage layout validations. ([#​1051](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/1051))

---

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 becomes conflicted, 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.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/highlight.js@11.10.0	None	0	5.35 MB	highlightjs_bot
npm/highlightjs-cairo@0.4.0	None	0	10.5 kB	ericglau
npm/highlightjs-solidity@2.0.6	None	0	42 kB	haltman
npm/path-browserify@1.0.1	None	0	54.3 kB	goto-bus-stop
npm/postcss-load-config@6.0.1	environment	0	22.7 kB	ai
npm/postcss@8.4.41	environment, filesystem	+1	203 kB	ai
npm/rollup-plugin-livereload@2.0.5	environment, network, shell	0	14.4 kB	thgh
npm/rollup-plugin-styles@4.0.0	environment, filesystem	+5	439 kB	anidetrix
npm/rollup-plugin-svelte@7.2.2	filesystem	+1	66.2 kB	dummdidumm
npm/rollup-plugin-terser@7.0.2	eval Transitive: environment, filesystem, unsafe	+2	6.88 MB	trysound
npm/rollup@4.21.1	environment, filesystem	+2	2.47 MB	lukastaegert
npm/sirv-cli@2.0.2	environment, filesystem, network	0	18.4 kB	lukeed
npm/svelte-check@3.8.6	Transitive: environment	+1	4.55 MB	svelte-language-tools-deploy
npm/svelte-preprocess@5.1.4	environment, filesystem	+1	629 kB	dummdidumm
npm/svelte@3.59.2	None	0	10.6 MB	conduitry
npm/tailwindcss@3.4.10	environment, filesystem	+5	5.89 MB	adamwathan
npm/tippy.js@6.3.7	environment	0	2.07 MB	atomiks
npm/tslib@2.7.0	None	0	86.2 kB	typescript-bot
npm/util@0.12.5	environment	0	33.7 kB	goto-bus-stop

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/svelte-preprocess@5.1.4	Install script: postinstall Source: echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."	packages/ui/package.json	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/svelte-preprocess@5.1.4