We were using a commit when installing forge-std as a dependency for vulcan. This is a problem because when you create a new forge project it comest with a tagged version installed that doesn't have all the cheatcodes that the commit could have. This means that if a user creates a new forge project and then installs vulcan on top the compilation will fail since the tagged version might not have the cheatcodes that we are using
To fix this:
1) Use the latest forge-std tagged release
2) Create interfaces to access new cheatcodes that are not yet released on that tag but that were included in foundry
We were using a commit when installing
forge-stdas a dependency for vulcan. This is a problem because when you create a new forge project it comest with a tagged version installed that doesn't have all the cheatcodes that the commit could have. This means that if a user creates a new forge project and then installs vulcan on top the compilation will fail since the tagged version might not have the cheatcodes that we are usingTo fix this: 1) Use the latest forge-std tagged release 2) Create interfaces to access new cheatcodes that are not yet released on that tag but that were included in foundry