Abigen produces bindings with dependency issues

[FrankieIsLost]

Version
439a0c7

Platform
MacOS

Description
#2222 seems to have affected binding generation. forge bind generates bindings which produce the following errors

error[E0432]: unresolved import `futures_util::try_join`
   |
35 | use futures_util::{lock::Mutex, try_join};
   |                                 ^^^^^^^^ no `try_join` in the root

error: cannot determine resolution for the macro `try_join`
    |
789 |             try_join!(self.resolve_field(ens_name, "avatar"), self.resolve_name(ens_name))?;
    |             ^^^^^^^^
    |
    = note: import resolution is stuck, try simplifying macro imports

    Checking ethers-contract-abigen v2.0.0 (https://github.com/gakonst/ethers-rs#439a0c7d)

Relatedly, should the generated Cargo.toml file pin ethers to a specific version?

[DaniPopes]

How can I reproduce this? And where is the error occurring?

[FrankieIsLost]

I believe it should be affecting all bindings generation, but you can use the same toy example from #2261. Adding it here as well:

Consider the following solidity code

pragma solidity ^0.8.13;

contract TestContract {
    event EmptyEvent();
}

Running forge bind --bindings-path ./bindings --crate-name bindings after a fresh foundryup generates rust code that produces the error

[DaniPopes]

Oh I see, it breaks on building the repo, even if you cd into it and build it there it's fine, I'm not sure what this is.
Can you try again after manually setting [package] ... resolver = "1" in Cargo.toml?