bug(soldeer): Error: data did not match any variant of untagged enum when adding Aave V3 Core dependency

[Progamermaker101]

I’m unable to add the Aave V3 Core dependency to my Foundry project. Other libraries (like OpenZeppelin) work fine, but Aave V3 triggers a “data did not match any variant of untagged enum” error. I’ve tried multiple tags, removing BOM, reinstalling Foundry, etc., but the error persists.

Environment
OS: Ubuntu 24.04.2 LTS (via WSL or native Linux)

Output of lsb_release -a:

Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04

Foundry Version:
forge --version
Forge Version: 1.0.0-stable

foundry.toml Configuration
[profile.default]
src = "src"
out = "out"
libs = ["lib"]
[dependencies]
aave-v3-core = { git = "https://github.com/aave/aave-v3-core.git", tag = "v1.19.4" }

Exact Steps Taken & What We've Tried
Initializing the Project
Ran forge init foundry-flashloan to create a new project.
Manually added the Aave V3 dependency to foundry.toml.
Verified other dependencies (e.g., OpenZeppelin) work fine.

Running forge build
Got:
Error: failed to extract foundry config;
foundry config error: data did not match any variant of untagged enum SoldeerDependencyValue
for setting 'dependencies.aave-v3-core'

Trying Different Aave V3 Versions
Attempted multiple tags, including:

tag = "v1.19.4"
tag = "v1.14.2"
branch = "master"
rev = "v1.14.2"

Also tried reinstalling Foundry & Cleaning the Environment
Tried:

bash
foundryup uninstall
rm -rf ~/.foundry ~/.config/foundry
foundryup
Then reinitialized the project with:

bash
forge init foundry-flashloan
forge install aave/[email protected]

Checking for Hidden Formatting Issues in foundry.toml
Checked for BOM (Byte Order Mark) Issues

Used xxd foundry.toml → No ef bb bf detected.
Used dos2unix foundry.toml → No change in error.
Recreated foundry.toml from Scratch

bash
rm foundry.toml
echo -e "[profile.default]\nsrc = "src"\nout = "out"\nlibs = ["lib"]\n\n[dependencies]\naave-v3-core = { git = "https://github.com/aave/aave-v3-core.git\", tag = "v1.19.4" }" > foundry.toml
Still fails on forge build.

Testing Other Dependencies
✅ OpenZeppelin Works: Installed OpenZeppelin using:

bash
forge install OpenZeppelin/openzeppelin-contracts
forge build worked fine.

❌ Aave V3 Core Fails:
Only Aave V3 Core produces this "data did not match any variant of untagged enum" error.

Expected: forge build should either successfully compile or at least process dependencies without error.
Actual: forge build fails with the SoldeerDependencyValue error, specifically for Aave V3 Core.

[zerosnacks]

cc @mario-eth this appears to be related to Soldeer

[mario-eth]

Hey i you missing the version field, even if you have the tag you still need the version = "v1.19.4"

aave-v3-core = { version = "v1.19.4", git = "https://github.com/aave/aave-v3-core.git", tag = "v1.19.4" }

alternatively you can use this command and it will automatically install it for you

forge soldeer install aave-v3-core~v1.19.4 https://github.com/aave/aave-v3-core.git --tag v1.19.4

I have to open an issue that if the tag is or commit is present when you install from git, then that should basically be the "version" field.

[beeb]

I think foundry should use a more relaxed approach to parsing the soldeer config and deps so that we can do the validation in soldeer later on. Also it should use the types we export from soldeer_core. This will give better error messages.