Eric Lau

Hi, thanks for reporting this. You can avoid this error by setting the [block_gas_limit](https://book.getfoundry.sh/reference/config/testing?highlight=block_gas_limit#block_gas_limit) configuration in your Foundry environment to a higher value, so that your script is able to...

>Additionally, in initContract() i want to pre-deploying contracts. If I don't do this, I'll get this error. ← [Revert] vm.getCode: no bytecode for contract; is it abstract or unlinked? └─...

We added checks to detect issues in parent initializer calls in [@openzeppelin/[email protected]](https://github.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin%2Fupgrades-core%401.42.0). In your scenario, since you are upgrading and if you don't need an initializer in your upgraded contract,...

The plugin currently doesn't validate reinitializers, but we may add https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/1122 to allow you to specify that your `initializeV2` function is the initializer that should be validated.

This is addressed in [@openzeppelin/[email protected]](https://github.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin%2Fupgrades-core%401.43.0) which allows you to annotate your reinitializer function with NatSpec `@custom:oz-upgrades-validate-as-initializer`, which will cause it to be validated as an initializer. See details in https://docs.openzeppelin.com/upgrades-plugins/writing-upgradeable#validating_initializers...

@EthixLucifer Sure, thanks. You can find development setup steps in the [readme](https://github.com/OpenZeppelin/contracts-wizard?tab=readme-ov-file#development).

Replaced by https://github.com/OpenZeppelin/contracts-wizard/pull/616

Replaced by https://github.com/OpenZeppelin/contracts-wizard/pull/560

This is somewhat related to https://github.com/OpenZeppelin/contracts-wizard/pull/335 , although that one specifically gives an error if the version is out of range. We could possibly support multiple versions using the same...

Can you revert the changelog and package.json version updates, and [add a changeset](https://github.com/OpenZeppelin/contracts-wizard/blob/master/CONTRIBUTING.md#adding-changesets) for `@openzeppelin/wizard-stylus` with type `minor`? This will handle the bump to `0.2.0` automatically during the release process.