Open holic opened 1 year ago
Might look into fixing this, very annoying
@meetmangukiya lmk if you want me to assign it to you!
Any solutions?
Last I checked forge update
was actually updating the submodules to the correct commits and not checking out the latest master on each submodule. But its just git showing and needing you to add them anyway. --recursive --checkout
is the correct way afaict.
@meetmangukiya still planning on taking this on? agree it's a bit annoying rn..else we're happy to own if it's a serious blocker for people
Check my previous comment. I didn't find a solution.
same issue here
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (3a15fe9 2023-01-29T00:06:04.108254Z)
What command(s) is the bug in?
forge update
Operating System
macOS (Apple Silicon)
Describe the bug
Running
forge update
on a particular dependency seems to do a recursive update of all of its forge dependencies (git submodules), which keeps me from being able to commit the update/changes for the dep I wanted to update.I would expect
forge update
to bump the dependency version to the latest, and then follow the checked-in submodule git hashes to update its dependencies (rather than also bumping those to the latest).To resolve this, I have to manually go in and check out each dependency's dependency to the submodule hash checked into the dependency's repo.
See also #2618