Pushed updated lock but continue inferring
Hi everyone.
I'm starting with python scripts
I my vs code y test the script with the "use current lock file" and i regenerate the Metadata for that script
Then i push the changes to the remote
When I test and deploy the script in the website, the lock file that be used by the script online continue be the old with inferred dependencies and lock file
How to allow or force use the pushed lock file?
1 Reply
When you test with the code editor, it will always infer dependencies, but when you run the deployed version it will always use your lockfile