bug: alexandria build requires specific commit hashes

[ccbbccbb]

Bug Report

Alexandria version:

commit hash: 6a989d636243494a0529fc3af06a924493499564

Current behavior:

note that this is specific to dojo as it defaults to using 2.8.4 -- when building with sozo (sozo build), alexandria only works with specific commit hash to resolve dependencies. without specifying a hash (e.g. relying on the default branch or rev-less spec), the build fails with a starknet version mismatch:

❯ sozo build
    Updating git repository https://github.com/keep-starknet-strange/alexandria
error: Version solving failed:
- alexandria_bytes v0.1.0 
(git+https://github.com/keep-starknet-strange/alexandria.git#162bed1c636d31ccaaa90ed3eb32c9eb1d5e3bd3) 
cannot use starknet v2.8.4 (std), because alexandria_bytes requires starknet ^2.9.2

Scarb does not have real version solving algorithm yet.
Perhaps in the future this conflict could be resolved, but currently,
please upgrade your dependencies to use latest versions of their dependencies.

Expected behavior:

simplify dependency management by removing the need to specify commit hashes.

Steps to reproduce:

1. add the following to scarb.toml:

alexandria_data_structures = { git = "https://github.com/keep-starknet-strange/alexandria.git" }

2. run sozo build w/ sozo 1.0.8.
3. observe error.
4. alternatively, explicitly include a commit hash to get the build working:

alexandria_data_structures = { git = "https://github.com/keep-starknet-strange/alexandria.git", rev = "6a989d636243494a0529fc3af06a924493499564" }

this works but is not ideal.

Related code:

specified above.

Other information:

updating release tags for the repository aligned with starknet versions (e.g., v2.8.4 or v2.9.2) would help.

example of how this could be done:

alexandria_data_structures = { 
git = "https://github.com/keep-starknet-strange/alexandria.git", 
tag = "v2.8.4"
}

[gaetbout]

I think @0xLucqs, this one is for you

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

[gaetbout]

@0xLucqs ?

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

[ermvrs]

Can you try with 0.3.0 or 0.2.0 version?