Make the crate generated by forge bind depend on alloy through crates.io instead of git

[guidanoli]

Component

Forge

Describe the feature you would like

Currently, when you run forge bind, it generates a crate (under out/bindings by default).
Below is the generated Cargo.toml file:

[package]
name = "foundry-contracts"
version = "0.1.0"
edition = "2021"

[dependencies] 
alloy = { git = "https://github.com/alloy-rs/alloy", features = ["sol-types", "contract"] }

This creates has some problem for projects that try to publish it to crates.io:

• It doesn't contain a license and description, which are required by crates.io. This is being tracked by Add options to forge bind to define crate description and license #6844.
• It depends on alloy through git, and not crates.io.

This issue is about the second item.
One solution is to edit this Cargo.toml with tomlq, but ideally we would like forge to generate the crate in a format that can already be published to crates.io without any extra intervention.

Below is the desired diff:

7c7
< alloy = { git = "https://github.com/alloy-rs/alloy", features = ["sol-types", "contract"] }
---
> alloy = { version = "0.12.4", features = ["sol-types", "contract"] }

Do note that we specified the version of alloy.
If not specified, Forge could specify one by default.

Additional context

No response

[mattsse]

@Soubhik-10 this is also similar

[Soubhik-10]

@Soubhik-10 this is also similar

Will try this too

[zerosnacks]

Hmm.. this PR #9861 modified the behavior of --alloy-version to install the crate via crates.io and introduced --alloy-rev as a way to install by tag or branch via Github

What version of Foundry are you using @guidanoli?

[guidanoli]

I'm using the latest stable release.

[zerosnacks]

@guidanoli would you mind trying this out on the latest nightly? foundryup -i nightly / foundryup --use nightly

[guidanoli]

Can confirm this works on the latest nightly, but when will this feature be available on a stable release?

[zerosnacks]

We are working towards a 1.1 release that we will hopefully be able to release a pre-release of early next month.

For now marking this as resolved - thanks!