ruby.git/lib/bundler/cli/lock.rb, branch v4.0.2

[rubygems/rubygems] Fix `bundle lock` regression when using `update` and `lockfile` flags:

2025-09-03T14:38:37+00:00

- Ref #8917
- ### Problem

  Prior to Bundler 2.5.6, running
  `bundle lock --update foo --lockfile Gemfile_bumped.lock` would
  update only the foo gem and write the lockfile to the
  `Gemfile_bumped.lock`.

  In Bundler 2.5.6 and above running the same command, updates
  absolutely all gems.
  This change is related to #7047

  ### Solution

  We decided to expose the `write_lock` method rather than going
  through a complex deprecation cycle of the `lock` method.

  This commit applies the same business logic as prios to 2.5.6 where,
  we build the definition using the existing lockfile, make changes to
  the definition and dump it into the desired lockfile.

https://github.com/rubygems/rubygems/commit/c88f00c41d

[rubygems/rubygems] Refactor handling platform removals

2025-02-25T06:36:46+00:00

And make it consistent with platform additions.

https://github.com/rubygems/rubygems/commit/64342ae404

[rubygems/rubygems] Fix `bundle lock --add-checksums`

2024-11-25T18:14:32+00:00

Due to a typo in the spec, the issue was not caught initially. If
Bundler does not need to re-resolve, `bundle lock` is a noop so Bundler
does not add checksums.

To fix the issue, we do something similar to what `bundle install` does,
just without actually installation. First set the domain (local or
remote) according to whether a re-resolve is necessary, and then
materialize lazy specifications into real specifications, so that
checksums are actually fetched from each source.

https://github.com/rubygems/rubygems/commit/84b6f4ee96

[rubygems/rubygems] Most of the times, eagerly resolving is not necessary

2024-11-25T18:14:31+00:00

All we need is to setup remote or local sources appropriately.

https://github.com/rubygems/rubygems/commit/3ceff46a2a

[rubygems/rubygems] Add `bundle lock --add-checksums` to add checksums to an existing lockfile

2024-11-08T10:27:03+00:00

https://github.com/rubygems/rubygems/commit/0a9c1ce60d

Normalize lockfile platforms

2024-10-26T09:44:15+00:00

[rubygems/rubygems] Reject unknown platforms when running `bundle lock --add-platform`

2024-08-29T09:59:26+00:00

https://github.com/rubygems/rubygems/commit/1f93a2bdc5

[rubygems/rubygems] Emit progress to stderr when `--print` is passed to `bundle lock`

2024-08-26T14:56:26+00:00

`bundle lock --print --update` can take a long time to fetch sources and
resolve the lock file.

Before, `--print` caused output to be completely silenced, so nothing
was printed at all until the resolved lock file is finally emitted to
stdout.

With this change, `--print` now prints progress to stderr. E.g.:

```
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
```

This provides a better user experience, especially when
`lock --print --update` takes several seconds or more.

The lock file is still printed to stdout, so tools consuming the lock
file on stdout will not be affected.

https://github.com/rubygems/rubygems/commit/6719baa700

[rubygems/rubygems] Refactor lockfile generation

2024-02-08T05:43:56+00:00

https://github.com/rubygems/rubygems/commit/6a0c03c77f

[rubygems/rubygems] Refactor: Move filesystem access into Definition class

2023-12-12T01:08:20+00:00

https://github.com/rubygems/rubygems/commit/2720da2659