| Age | Commit message (Collapse) | Author |
|---|
| Because get_push_scope is a method call, Ruby will allocate an array for *args even though it is not necessary to do so. Using a local variable avoids the allocation. Found by the performance warning in Ruby feature 21274. https://github.com/rubygems/rubygems/commit/0473c0cf32 |
| This decouples `gem exec` behavior (and tests) from the sort order of the gemspec. https://github.com/rubygems/rubygems/commit/911cd29159 |
| When `gem exec foo` is run, and "foo" is a gem that has multiple executables, none of them named "foo", raise an error explaining the situation and telling user to be more specific. Currently the first command in the executables array is run, but this may come as surprising sometimes, so better raise an error. https://github.com/rubygems/rubygems/commit/acda5d8f6e Notes: Merged: https://github.com/ruby/ruby/pull/12968 |
| There are 3 possible locations: - $HOME/.gem/credentials - $XDG_DATA_HOME/gem/credentials - $HOME/.local/share/gem/credentials https://github.com/rubygems/rubygems/commit/c51756b96e |
| https://github.com/rubygems/rubygems/commit/0c3a65871a |
| https://github.com/rubygems/rubygems/commit/d8d68cc00e |
| That's indeed the ideal behavior but it's a mess to maintain because the version of RubyGems shipped with each patchlevel of Ruby changes. We could try looking at the `VERSION` constant in ` RbConfig::CONFIG["rubylibdir"` but for now I calling what's in there now as good enough. https://github.com/rubygems/rubygems/commit/40ccf2b093 |
| We already do this check in `setup.rb` itself, which is run earlier. https://github.com/rubygems/rubygems/commit/160cc3f1c5 |
| https://github.com/rubygems/rubygems/commit/31fadaf2d2 |
| output The $0 value is used in many CLI libraries to determine the name of the application, when displaying help and error messages. Without setting this value, it defaults to `gem` which can be confusing. Before: ``` $ gem exec kamal help Commands: gem accessory # Manage accessories (db/redis/search) gem app # Manage application gem audit # Show audit log from servers gem build # Build application image gem config # Show combined config (including secrets!) gem deploy # Deploy app to servers gem details # Show details about all containers gem docs [SECTION] # Show Kamal configuration documentation gem help [COMMAND] # Describe available commands or one specific command gem init # Create config stub in config/deploy.yml and secrets stub in .kamal gem lock # Manage the deploy lock gem proxy # Manage kamal-proxy gem prune # Prune old application images and containers gem redeploy # Deploy app to servers without bootstrapping servers, starting kamal-proxy, pruning, and registry login gem registry # Login and -out of the image registry gem remove # Remove kamal-proxy, app, accessories, and registry session from servers gem rollback [VERSION] # Rollback app to VERSION gem secrets # Helpers for extracting secrets gem server # Bootstrap servers with curl and Docker gem setup # Setup all accessories, push the env, and deploy app to servers gem upgrade # Upgrade from Kamal 1.x to 2.0 gem version # Show Kamal version ``` After: ``` $ gem exec kamal help Commands: kamal accessory # Manage accessories (db/redis/search) kamal app # Manage application kamal audit # Show audit log from servers kamal build # Build application image kamal config # Show combined config (including secrets!) kamal deploy # Deploy app to servers kamal details # Show details about all containers kamal docs [SECTION] # Show Kamal configuration documentation kamal help [COMMAND] # Describe available commands or one specific command kamal init # Create config stub in config/deploy.yml and secrets stub in .kamal kamal lock # Manage the deploy lock kamal proxy # Manage kamal-proxy kamal prune # Prune old application images and containers kamal redeploy # Deploy app to servers without bootstrapping servers, starting kamal-proxy, pruning, and registry login kamal registry # Login and -out of the image registry kamal remove # Remove kamal-proxy, app, accessories, and registry session from servers kamal rollback [VERSION] # Rollback app to VERSION kamal secrets # Helpers for extracting secrets kamal server # Bootstrap servers with curl and Docker kamal setup # Setup all accessories, push the env, and deploy app to servers kamal upgrade # Upgrade from Kamal 1.x to 2.0 kamal version # Show Kamal version ``` https://github.com/rubygems/rubygems/commit/4fd060b96d |
| Signed-off-by: Samuel Giddins <segiddins@segiddins.me> https://github.com/rubygems/rubygems/commit/a5412d9a0e |
| executables around https://github.com/rubygems/rubygems/commit/4b81add54c |
| A default gem does not always live in the same place. For example, Bundler may be installed to `site_dir` when RubyGems have been upgraded. A more reliable way seems to actually activate the default gem, so that we can know for sure where it lives. https://github.com/rubygems/rubygems/commit/c69f6dfb18 |
| https://github.com/rubygems/rubygems/commit/1cfc1d626c |
| https://github.com/rubygems/rubygems/commit/c9e665eb8a |
| Since `Gem::Uninstaller` no longer changes paths either. https://github.com/rubygems/rubygems/commit/427059d45f |
| https://github.com/rubygems/rubygems/commit/511c7b211b |
| https://github.com/rubygems/rubygems/commit/032b3c518a |
| https://github.com/rubygems/rubygems/commit/5887e6dfa1 |
| Nothing is actually raising this at the moment. https://github.com/rubygems/rubygems/commit/3b824ca7a6 |
| Notes: Merged: https://github.com/ruby/ruby/pull/11491 |
| default gems https://github.com/rubygems/rubygems/commit/29357a5dd6 |
| (https://github.com/rubygems/rubygems/pull/6483) https://github.com/rubygems/rubygems/commit/41d8cffd2e Co-Authored-By: MSP-Greg <Greg.mpls@gmail.com> |
| |
| user installed gems" This reverts commit a3edc4abc574b04bcacfae2af188cce7d27bfcf1. That commit caused test failure with Windows platform. * https://github.com/ruby/ruby/actions/runs/9289018414/job/25561871390 * https://github.com/ruby/ruby/actions/runs/9289018425/job/25561873060 |
| installed gems https://github.com/rubygems/rubygems/commit/0eb6ed8f86 |
| `--destdir` is given This was only working for gems also installed in the default gem home. https://github.com/rubygems/rubygems/commit/47df02dbd9 |
| https://github.com/rubygems/rubygems/commit/5fbe5e43d6 |
| https://github.com/rubygems/rubygems/commit/4158034d89 |
| https://github.com/rubygems/rubygems/commit/3c4e3fadc9 |
| GemspecHelpers. https://github.com/rubygems/rubygems/commit/2f80a595c4 |
| https://github.com/rubygems/rubygems/commit/701550f9dd |
| suggest passing --diff. https://github.com/rubygems/rubygems/commit/7caadd182c |
| doesn't match. https://github.com/rubygems/rubygems/commit/a691170dc7 |
| https://github.com/rubygems/rubygems/commit/8644ce7193 |
| https://github.com/rubygems/rubygems/commit/4446389f2e |
| working directory. https://github.com/rubygems/rubygems/commit/f2e4e5b56f |
| https://github.com/rubygems/rubygems/commit/3e9545193a |
| https://github.com/rubygems/rubygems/commit/3b88553d0d |
| https://github.com/rubygems/rubygems/commit/6d661573f0 |
| https://github.com/rubygems/rubygems/commit/bcbe6f7b7a |
| |
| https://github.com/rubygems/rubygems/commit/b7d2de2ba8 |
| The fact that under the hood the upgrade is done through a rubygems-update gem is an implementation detail that does not really help users to know. Plus, it reads a bit weird. https://github.com/rubygems/rubygems/commit/0fa5c50258 |
| https://github.com/rubygems/rubygems/commit/36052abbe2 |
| https://github.com/rubygems/rubygems/commit/701980b240 |
| https://github.com/rubygems/rubygems/commit/f25013bcc0 |
| https://github.com/rubygems/rubygems/commit/34df962cf4 |
| https://github.com/rubygems/rubygems/commit/7576c21295 |
| It's the `Gem::Installer` below what installs executables, and the code being deleted here is now actually creating a `gems/` folder in the root of the source repo when running `ruby setup.rb`. https://github.com/rubygems/rubygems/commit/0e69a8b0d6 |
