summaryrefslogtreecommitdiff
path: root/spec
AgeCommit message (Collapse)Author
2025-09-26[rubygems/rubygems] add loading support on Windowssodacris
https://github.com/rubygems/rubygems/commit/04574ba59a
2025-09-26[rubygems/rubygems] skip checking title on Windows because it's not supportedsodacris
https://github.com/rubygems/rubygems/commit/fd2c54f371
2025-09-19[rubygems/rubygems] Switch `cache_all` to be `true` by defaultDavid Rodríguez
And make it a standard setting. https://github.com/rubygems/rubygems/commit/17e356fa94
2025-09-19[rubygems/rubygems] Completely remove passing `--ext` to `bundle gem` ↵David Rodríguez
without a value https://github.com/rubygems/rubygems/commit/9f34bf6854 Co-authored-by: Martin Emde <martinemde@users.noreply.github.com>
2025-09-19[rubygems/rubygems] Switch `lockfile_checksums` to be true by defaultDavid Rodríguez
https://github.com/rubygems/rubygems/commit/47c3dc19ee Co-authored-by: Jonathan Barquero <jonbarlo@hotmail.com>
2025-09-19[rubygems/rubygems] Make `bundle show --outdated` raise an errorDavid Rodríguez
https://github.com/rubygems/rubygems/commit/3bbbf4a4e5
2025-09-19[rubygems/rubygems] Make `--local-git` flag to `bundle plugin install` raise ↵David Rodríguez
an error https://github.com/rubygems/rubygems/commit/8bfe317e6d
2025-09-19[rubygems/rubygems] Fix parallel installation issueDavid Rodríguez
If using a gem with precompiled versions having different dependencies than the generic version from a path source, and with a lockfile including a precompiled version, we would materialize the generic version, but end up using dependencies for the precompiled version. That will result in the parallel installer missing the specifications for the extra dependencies of the generic version, causing a crash. If we are materializing for installation, make sure we use the materialized specification when traversing dependencies. https://github.com/rubygems/rubygems/commit/5f75d75de7
2025-09-18Bump rexmldependabot[bot]
Bumps the bundler group with 1 update in the /spec/bundler/realworld/fixtures/warbler directory: [rexml](https://github.com/ruby/rexml). Updates `rexml` from 3.4.1 to 3.4.2 - [Release notes](https://github.com/ruby/rexml/releases) - [Changelog](https://github.com/ruby/rexml/blob/master/NEWS.md) - [Commits](https://github.com/ruby/rexml/compare/v3.4.1...v3.4.2) --- updated-dependencies: - dependency-name: rexml dependency-version: 3.4.2 dependency-type: indirect dependency-group: bundler ... Signed-off-by: dependabot[bot] <support@github.com>
2025-09-17bundled_gems_spec.rb: Remove useless `map`Nobuyoshi Nakada
`Dir.[]` returns list of strings, `map(&:to_s)` does nothing.
2025-09-17[rubygems/rubygems] Finalize `bundle install --binstubs` removalDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ccb65ce0ea
2025-09-17[rubygems/rubygems] Make `bundle remove --install` raise an errorDavid Rodríguez
https://github.com/rubygems/rubygems/commit/444022cfd3
2025-09-16[rubygems/rubygems] Remove aggregate source mentionsDavid Rodríguez
It's a term from times with multiple remote sources, let's move on :) https://github.com/rubygems/rubygems/commit/6439b8944e
2025-09-16[rubygems/rubygems] Completely remove multisources supportDavid Rodríguez
https://github.com/rubygems/rubygems/commit/8f9d6c54a1
2025-09-16[rubygems/rubygems] Remove `allow_offline_install` settingDavid Rodríguez
And let the feature always be enabled, so I'm not sure why we'd need this configurable. https://github.com/rubygems/rubygems/commit/5a27f0c1e3
2025-09-16[rubygems/rubygems] Complete rubocop flags and settings removalDavid Rodríguez
If the CLI flags are used, we abort early as usual. As per the settings, I decided to ignore them. We've been migrating them automatically to the new name for a long time and we don't yet have a standard way to deprecate and remove settings (we should probably use the existing setting validators). So I think it's fine for now to do what we normally do (ignore the setting). https://github.com/rubygems/rubygems/commit/8311de6e69
2025-09-16[rubygems/rubygems] Fix `--no-rubocop` deprecation messageDavid Rodríguez
https://github.com/rubygems/rubygems/commit/2c16b0e11e
2025-09-16Fix a function name typo in the description [ci skip]Nobuyoshi Nakada
2025-09-14Remove tests do not test Regexp methodsNobuyoshi Nakada
The backslashs in these tests are parsed as escapes in string literals by the parser, but not passed to the `Regexp` methods.
2025-09-12Fix use of uninitialized memory in stringsPeter Zhu
Strings created from the C API with a len but no ptr have a buffer allocated and the length set, but the buffer is not zero'd. This causes use of uninitialized memory and allows reading memory that previously existed there. For example, the rb_str_tmp_new spec fails when we create a string with a large length greater than 24 bytes (since we zero the first 24 bytes of the slot).
2025-09-12[rubygems/rubygems] Fix outdated lockfile during `bundle lock` when source ↵Earlopain
changes When the source used to be git and switches back to rubygems, it is possible that the git source contains a version that ruybgems doesn't know about yet. So don't add the locked spec to the base resolve, and also don't add a lower bound requirement on the version, since the version in the new source may actually be lower. https://github.com/rubygems/rubygems/commit/85514e3a1e
2025-09-12[rubygems/rubygems] Raise error on missing version fileMatheus Richard
If the file option is given but the file not found, raise a GemfileError with a message indicating the file was not found. Currently this is raising a generic Errno::ENOENT error. https://github.com/rubygems/rubygems/commit/db61de6b21
2025-09-11Don't load set_spec.c if not Ruby 3.5Peter Zhu
2025-09-11Fix compilation of set_spec.c for previous Ruby versionsPeter Zhu
Set was moved to C only in Ruby 3.5, so it does not compile on Ruby 3.4 and earlier.
2025-09-11[rubygems/rubygems] Remove spec originally meant to test remembering CLI flagsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/4919e5ca53
2025-09-11[rubygems/rubygems] Complete remembered options removalDavid Rodríguez
https://github.com/rubygems/rubygems/commit/573ffad3ea
2025-09-11[rubygems/rubygems] Introduce a way to ensure that removed flags get their ↵David Rodríguez
docs removed, too https://github.com/rubygems/rubygems/commit/a727b50697
2025-09-11[rubygems/rubygems] Remove deprecated usages of `bundle install ↵David Rodríguez
--deployment` during specs https://github.com/rubygems/rubygems/commit/c903afbc3f
2025-09-11[rubygems/rubygems] Remove implementation of `deployment`, `capistrano` and ↵David Rodríguez
`vlad` entrypoints Now they only raise an error. https://github.com/rubygems/rubygems/commit/6e7c8db151
2025-09-11[rubygems/rubygems] Completely remove `Bundle.*clean*` and ↵David Rodríguez
`Bundler.environment` helpers https://github.com/rubygems/rubygems/commit/e1b8bdcede
2025-09-08Add spec for missing or faulty `to_proc` methodsJean Boussier
Followup: https://github.com/ruby/ruby/pull/14463
2025-09-05[rubygems/rubygems] Improve error message when `path` and `gemspec` point to ↵manabeai
the same gem in Gemfile https://github.com/rubygems/rubygems/commit/e47a9064be
2025-09-04feature_spec.rb: Don't test --enable-all with --zjit*Takashi Kokubun
2025-09-04rubyopt_spec.rb: Stop testing JIT optionsTakashi Kokubun
in child processes. `make test-spec SPECOPTS="spec/ruby/command_line/rubyopt_spec.rb -T --yjit"` fails because `ruby_exe` doesn't seem to propagate options to child processes.
2025-09-03[rubygems/rubygems] Deprecate `bundle cache --frozen` and `bundle cache ↵David Rodríguez
--no-prune` Since they are remembered flags, too. I also restored a previous spec about `--frozen`, but didn't bother with `--no-prune`. https://github.com/rubygems/rubygems/commit/7802f016fc
2025-09-03[rubygems/rubygems] Improve `deprecations` helperDavid Rodríguez
Previous implementation included an empty element in the list of deprecations. https://github.com/rubygems/rubygems/commit/59eb233039
2025-09-03[rubygems/rubygems] Add another spec for yet another issue fixed by the ↵David Rodríguez
previous patch https://github.com/rubygems/rubygems/commit/fbb8340186
2025-09-03[rubygems/rubygems] Add extra spec for another issue that the previous patch ↵David Rodríguez
fixed https://github.com/rubygems/rubygems/commit/4fc57c69b2
2025-09-03[rubygems/rubygems] Fix `bundle cache` failing in frozen mode if ↵David Rodríguez
vendor/cache is empty https://github.com/rubygems/rubygems/commit/36c5af9156
2025-09-03[rubygems/rubygems] Improve spec wording and implementationDavid Rodríguez
Limit the `before` block to set `frozen`, which is the context of the spec, and change the implementation to only write the Gemfile once, with a gem being removed from what's in the lockfile. https://github.com/rubygems/rubygems/commit/4d0314ff37
2025-09-03[rubygems/rubygems] It's not necessary to set `deployment`David Rodríguez
https://github.com/rubygems/rubygems/commit/eaa51203ca
2025-09-03[rubygems/rubygems] Remove unnecessary installDavid Rodríguez
Since the path is changed later by the `deployment` setting, it makes no difference. So just create a lockfile. https://github.com/rubygems/rubygems/commit/2dd6f65642
2025-09-03[rubygems/rubygems] Remove unnecessary subject from one specDavid Rodríguez
https://github.com/rubygems/rubygems/commit/a761581e89
2025-09-03[rubygems/rubygems] Fix `bundle lock` regression when using `update` and ↵Edouard CHIN
`lockfile` flags: - 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
2025-09-03Completely remove `bundle viz` commandDavid Rodríguez
2025-09-03Completely remove `bundle inject` commandDavid Rodríguez
2025-09-03[rubygems/rubygems] Introduce `SharedHelpers.feature_removed!`David Rodríguez
To directly raise regardless of version. https://github.com/rubygems/rubygems/commit/38fb97cffa
2025-09-03[rubygems/rubygems] No need to print caller location when raising directlyDavid Rodríguez
https://github.com/rubygems/rubygems/commit/6c2b06cc16
2025-09-03[rubygems/rubygems] Ensure removed commands get their docs removed, tooDavid Rodríguez
https://github.com/rubygems/rubygems/commit/2a2e45bbe9
2025-08-29Shrink ruby_bug version guard in anticipation of 3.4.6 releaseAlan Wu
Fix for this bug was merged into ruby_3_4 in 5a42d267bfabc86f86cae2e83de24b1b86bc316a and should go out in the next 3.4.x release.
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-18 09:53:51 +0000