Deno manager failed to update frozen lock file #43055
-
How are you running Renovate?A Mend.io-hosted app Which platform you running Renovate on?GitHub.com Which version of Renovate are you using?43.159.2 Please tell us more about your question or problemWhen I enforce the lock file to be frozen in https://github.com/5ouma/reproxy/blob/e17c7f50/deno.json#L10 Logs (if relevant)Logs |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Thank you for trying it out so quickly! I think that the lock file should not be updated when In this case, Package managers usually update lock files automatically regardless of Deno. It often provides an option to freeze lock files in their commands to prevent unintended dependencies from being introduced in CI. So, very few package managers have a property in their configuration file that instructs them to freeze lock files. Yarn also has a similar property, though. I think it's better approach to allow the behavior of |
Beta Was this translation helpful? Give feedback.
Thank you for trying it out so quickly!
I think that the lock file should not be updated when
frozen: trueis set. This is because it indicates that whoever does not want to update the lock file, regardless of the user's machine or CI environment, such as Renovate.In this case,
deno install --frozenis the desired behaviour that Renovate should execute operations according to the input in thedeno.jsonfile.Package managers usually update lock files automatically regardless of Deno. It often provides an option to freeze lock files in their commands to prevent unintended dependencies from being introduced in CI. So, very few package managers have a property in their configuration file th…