Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from rubygems:master #2

Open
wants to merge 1,217 commits into
base: master
Choose a base branch
from
Open

Conversation

pull[bot]
Copy link

@pull pull bot commented Jun 12, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Jun 12, 2024
deivid-rodriguez and others added 29 commits December 11, 2024 17:18
The --changelog and --no-changelog flags are missing from docs, this adds them in a way that matches other flags
Avoid UTF-32 and UTF-16 strings with trailing bytes in truffleruby
…entation-of-command-flags

Normalize command flag documentation and make sure all flags are documented
…-deps

Bump vendored uri, securerandom, and net-http
Not everything needs to be run from the `bundler/` subfolder now.
…utput

Don't print a bunch of blank lines when setting up dependencies
Use Process.argv0 instead of $PROGRAM_NAME because $PROGRAM_NAME is
liable to be changed but Process.argv0 is not.
Fix restarting with locked version when `$PROGRAM_NAME` has been changed
deivid-rodriguez and others added 30 commits January 24, 2025 17:58
LoadError is not a RuntimeError.
This local variable is initialized later on in this file.
At this point, `dep.autorequire` is always nil.
If a gem has an internal error, that should not make `bundle console`
print the bug report template.
Since bundler now requires 3.3.1, we no longer need to do respond_to?
check before setting thread name.
Fix `bundle console` printing bug report template incorrectly
Remove respond_to? check for Thread#name=
[DOC] Undocument vendored everything
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.28.4 to 3.28.5.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@ee117c9...f6091c0)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
…ub/codeql-action-3.28.5

Bump github/codeql-action from 3.28.4 to 3.28.5
Bumps [ruby/setup-ruby](https://github.com/ruby/setup-ruby) from 1.213.0 to 1.214.0.
- [Release notes](https://github.com/ruby/setup-ruby/releases)
- [Changelog](https://github.com/ruby/setup-ruby/blob/master/release.rb)
- [Commits](ruby/setup-ruby@28c4ded...1287d2b)

---
updated-dependencies:
- dependency-name: ruby/setup-ruby
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
…/setup-ruby-1.214.0

Bump ruby/setup-ruby from 1.213.0 to 1.214.0
- Fix #8427
- Similar to 7cd19d8.
  Tweaked a bit the test supposed to prevent this error by checking
  whether the dep respond to these methods.
- We keep 2 list of supported ruby versions and each time a new ruby
  version is released we need to maintain both list. Forgetting
  to update one would prevent users from adding gem for a specific
  plaftorm (i.e. 7cd19d8 and 5462322).

  Extracted the list from the Dependency class and moved it to the
  CurrentRuby class (which I believe was originally added for that
  reason).
- Similar change than 29a1be0,
  keep a single source of truth where we store the platform.

  The only change worth highlighing is the platform "maglev".
  It was not part of the supported platform of dependencies,
  so calling `gem 'foo', plaftorm: 'maglev'` would not work.
  However, it was supposed to according to 45ec86e.
  That's why it was possible to do `Bundler.current_ruby.maglev?` or
  `Bundler.current_ruby.maglev_30?`.

  I didn't change the current behaviour and maglev is not supported,
  though I kept the `*maglev` methods as I believe CurrentRuby is
  public API.
Add ruby_34 and ruby_35 as valid platform:
These gems always define their main namespace and I don't think that
will ever change.
…ssary-console-fallback

Fix `bundle console` unnecessarily trying to load IRB twice
…ng-bundler-binstubs

Stop generating binstubs for Bundler itself
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.