Closed mmv08 closed 2 months ago
My understanding is that as the script has a bug fix, new version would be v0.3.1. Curious to know why there is v0.3.0-1 as new version instead? I couldn't find it as a convention in npm docs.
My understanding is that as the script has a bug fix, new version would be v0.3.1. Curious to know why there is v0.3.0-1 as new version instead? I couldn't find it as a convention in npm docs.
There is no bug in the script or the contracts per se. The bug is in the surrounding tooling. We had problems with NPM where it would generate a platform-specific lockfile and refuse to regenerate it on other platforms. This led the v0.3.0
to be only usable to deploy or verify contracts on the platform where the lockfile was generated, which happens to be Linux.
The version number suggestion came from Nick here
This PR:
Nothing to compile No need to generate any newer typings. reusing "SafeModuleSetup" at 0x2dd68b007B46fBe91B9A7c3EDa5A7a1063cB5b47 reusing "Safe4337Module" at 0x75cf11467937ce3F2f357CE24ffc3DBF8fD5c226