| Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/0c3a65871a
|
|
https://github.com/rubygems/rubygems/commit/d8d68cc00e
|
|
to be conservative
When converging specification to pass the set of versions that should be
preserved from the lockfile during resolution, we should make sure all
top level gems are considered, and only exclude those gems themselves
(and not their dependencies) if their locked versions happen to not be
satisfied by an edited Gemfile.
https://github.com/rubygems/rubygems/commit/ed2f1b7b88
|
|
For consistency with other specs.
https://github.com/rubygems/rubygems/commit/a5b2449896
|
|
https://github.com/rubygems/rubygems/commit/c519830d4d
|
|
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
|
|
* bundler/lib/bundler/templates/newgem/README.md.tt (Development): Use the
test_task value to get the correct test task name ("test", not "test-unit").
* bundler/spec/commands/newgem_spec.rb (README.md): Add tests for test task
names for each test frameworks.
https://github.com/rubygems/rubygems/commit/2a24708a63
|
|
verbose mode
https://github.com/rubygems/rubygems/commit/585a6a89d4
|
|
https://github.com/rubygems/rubygems/commit/09e0971ab8
|
|
https://github.com/rubygems/rubygems/commit/9e0018d9fe
|
|
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
|
|
https://github.com/rubygems/rubygems/commit/e7f5f067e8
|
|
In particular, when a gem registry transitive dependency is changed to a
git source direct dependency.
https://github.com/rubygems/rubygems/commit/bcdc7660d9
|
|
https://github.com/rubygems/rubygems/commit/1fc1e74f4d
|
|
https://github.com/ruby/ruby/actions/runs/11948300522/job/33305664284?pr=12139
```
IO#wait [events, timeout] passed changes thread status to 'sleep' when waits for WRITABLE event FAILED
Expected false == "sleep"
to be truthy but was false
D:/a/ruby/ruby/src/spec/ruby/library/io-wait/wait_spec.rb:99:in 'block (3 levels) in <top (required)>'
D:/a/ruby/ruby/src/spec/ruby/library/io-wait/wait_spec.rb:8:in '<top (required)>'
```
Notes:
Merged: https://github.com/ruby/ruby/pull/12140
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12137
|
|
Spec::BuildMetadata is only called from BundlerBuilder.
The current code is broken to call Spec::Builders#build_* method directly.
https://github.com/rubygems/rubygems/commit/4922ae40dd
|
|
https://github.com/rubygems/rubygems/commit/51854e1982
|
|
https://github.com/rubygems/rubygems/commit/3f39571181
|
|
Signed-off-by: Andrew Nesbitt <andrewnez@gmail.com>
https://github.com/rubygems/rubygems/commit/897819da36
|
|
the overwritten binstub in the test has a final new line that makes it
not match "OMG" exactly from the beginning, that's why the test passes,
but `bintubs` command without `--force` flag is not supposed to update
the binstub.
This change fixes the test to test what's supposed to update the
binstub, and also fixes the assertion that that it will fail in the
future if `--force` stops updating the binstub.
https://github.com/rubygems/rubygems/commit/dfc9023337
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12114
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12111
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12111
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12111
|
|
at test-bundled-gems
Notes:
Merged: https://github.com/ruby/ruby/pull/12111
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12111
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12110
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12098
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12098
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12098
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12098
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12096
|
|
In #225 it was reported that the output looks incorrect:
```
$ cat /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb
def x.y.z
end
$ ruby /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb
/tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb: --> /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb
expected a delimiter to close the parametersunexpected '.', ignoring it
> 1 def x.y.z
> 2 end
```
Specifically:
```
expected a delimiter to close the parametersunexpected '.', ignoring it
```
However this does not show up when executing the debug executable:
```
$ bin/bundle exec exe/syntax_suggest /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb
--> /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb
expected a delimiter to close the parameters
unexpected '.', ignoring it
> 1 def x.y.z
> 2 end
```
This is because `exe/syntax_suggest` uses STDOUT.puts while calling `ruby` with the filename uses a fake IO object represented by MiniStringIO. This class was incorrectly not adding a newline to the end of the print.
The fix was to move the class to it's own file where it can be tested and then fix the behavior.
close https://github.com/ruby/syntax_suggest/pull/225
https://github.com/ruby/syntax_suggest/commit/d2ecd94a3b
Co-authored-by: Andy Yong <andyywz@gmail.com>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12086
|
|
This will add +MOD_GC to the version string and Ruby description when
Ruby is compiled with shared gc support.
When shared GC support is compiled in and a GC module has been loaded
using RUBY_GC_LIBRARY, the version string will include the name of
the currently active GC as reported by the rb_gc_active_gc_name function
in the form
+MOD_GC[gc_name]
[Feature #20794]
Notes:
Merged: https://github.com/ruby/ruby/pull/11872
|
|
This reverts commit https://github.com/rubygems/rubygems/commit/82b25dd75afd.
https://github.com/rubygems/rubygems/commit/16adf53f23
|
|
Only in CI, if two different test runs are started (like `bin/rake
spec:all` does), the second one would not install the dev version of
Bundler and would fail to start.
This commit makes it work the same locally and in CI.
https://github.com/rubygems/rubygems/commit/7a5ca6c40f
|
|
https://github.com/rubygems/rubygems/commit/8b6f9b7f05
|