You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Ref #8917
- ### Problem
In 6a0c03c, we introduced a
deprecation that would disallow calling `lock("NewGemfile.lock")`.
The intention was that the lockfile target should be passed when
constructing a Definition object.
With this deprecation, it is no longer possible to create a
Definition from an existing lockfile, make changes to the
definition, and dump its content into a new lockfile.
This behaviour is used as public API but also internally with
the `bundle lock` command (currently broken, a fix will follow up
thanks to this commit).
### Solution
Remove the deprecation and introduce a new one related to the
position of the passed arguments. The method's signature is now:
`lock(preserve_unknown_section = false, target_lock = lockfile)`
0 commit comments