Closed tserg closed 6 months ago
Lock files not updating in sub-packages seems like a Scarb bug to me, if you care to investigate/report to the SWM team.
Lock files not updating in sub-packages seems like a Scarb bug to me, if you care to investigate/report to the SWM team.
I have checked with the Scarb team in Discord. I will proceed to merge first.
Lock files not updating in sub-packages seems like a Scarb bug to me, if you care to investigate/report to the SWM team.
To close the loop on this, the Scarb team clarified on Discord that "scarb will created only one lock file for the whole workspace, no matter when you run it. It will be created in the workspace root besides the workspace manifest."
Hence, this is expected behaviour.
This PR bumps
snfoundry
andsncast
to0.23.0
.While running
scarb update
, I noticed that theScarb.lock
files inscripts/deployment
andscripts/simulation
were not updated despite bumpingsncast
to0.23.0
andscarb update
in their respective directories. I think their lockfiles are now ignored since all their dependencies are inherited from thescripts
workspace, and hence I have deleted them.