Francisco Giordano

The config object is still not available in `truffle exec` so this still doesn't work. However, a user proposed a workaround in https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/761#issuecomment-1479396644

The current idea is to add an annotation that can state the intent to use a struct at a specific location. ```solidity /// @custom:storage-location L struct S { ... }...

@bh2smith I took a quick look at your PR. Having to manually fill in the values for a `ContractTransaction` is definitely bad. It makes sense for the default deployer which...

This is something we're interested in but are not prioritizing at the moment. If anyone is interested in this feature for their setup let us know!

We need someone to help us understand what the dry run does exactly and what is going wrong that it breaks the Upgrades Plugin. In the meantime, please use `--skip-dry-run`.

Hi @marsrobertson, it was a design decision to leave this out of scope of the plugins, which is why the proxy address is not stored in `.openzeppelin`. We expect users...

Yeah you can also use a json file to store the addresses, and read the json file in your scripts. I'm not aware of any articles about this but I...

A naive implementation would not be correct because structs don't necessarily align in storage the same way as their contents. We've seen this recently with `struct Timestamp { uint64 t;...

The key part here is the metadata hash as it enables us to check even in the presence of immutable variables. See [Contract Metadata](https://docs.soliditylang.org/en/latest/metadata.html).

We should improve the error check to better detect this situation and suggest running `hardhat node` to fix it.