forked from rubygems/rubygems
-
Notifications
You must be signed in to change notification settings - Fork 0
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
pull
wants to merge
1,217
commits into
47-studio-org:master
Choose a base branch
from
rubygems:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Support new rdoc plugin
LoadError is not a RuntimeError.
It's simpler.
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
- 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:
…y-ci Refactor JRuby CI
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )