summaryrefslogtreecommitdiff
path: root/bundler.gemspec
Commit message (Collapse)AuthorAgeFilesLines
* [repo move] Update GitHub URL in bundler.gemspec.Ellen Marie Dash2020-01-161-3/+3
|
* Remove misleading comment in GemfileDavid Rodríguez2019-08-101-4/+1
| | | | | Since we no longer use `git` to find out the list of files, the comment is misleading.
* Drop rubygems 2.5.0 and 2.5.1 supportdrop_rubygems_2_5_0_and_2_5_1_supportDavid Rodríguez2019-07-111-1/+1
|
* Remove development dependencies from gemspecremove_add_development_dependency_from_gemspecDavid Rodríguez2019-07-081-7/+0
| | | | And refactor development setup.
* Bump rubocop to 0.72.0David Rodríguez2019-07-081-1/+1
|
* Lock rubocop-performance to 1.4.0rubocop_071David Rodríguez2019-06-201-1/+1
|
* Bump rubocop to 0.71David Rodríguez2019-06-201-1/+1
|
* Bump Rubocop versionNate Holland2019-05-051-1/+1
| | | | | I was hoping this would turn up new cops or changes. It did not end up changing anything.
* Bump rubocop to 0.68.0rubocop_0_68David Rodríguez2019-04-301-1/+2
|
* One more compatibility cleanupmore_compatibility_cleanupDavid Rodríguez2019-04-281-7/+2
|
* Use `require_relative` in bundler's gemspecgemspec_require_relativeDavid Rodríguez2019-04-231-2/+2
|
* Remove mustache depremove_mustache_depDavid Rodríguez2019-03-191-1/+0
|
* Remove git subshelling from gemspecDavid Rodríguez2019-03-051-2/+1
|
* Auto-correct `Style/Encoding` rubocop issuesDavid Rodríguez2019-03-041-1/+0
|
* Bump rubocop to 0.65.0David Rodríguez2019-03-011-1/+1
| | | | Fix config and regenerate TODO config.
* Fixup r66984. Update the location of bundler gemspec.SHIBATA Hiroshi2019-02-201-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66993 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Remove rdiscount indirect dependencyremove_rdiscount_indirect_dependencyDavid Rodríguez2019-02-111-1/+0
| | | | | | We don't use this dependency directly so this is not needed. We put it there at some point because we needed to pin to a specific version, but that's no longer the case.
* Merge #6926Bundlerbot2019-01-241-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6926: Move Rubocop development dependency into gemspec r=hsbt a=alyssais ### What was the end-user problem that led to this PR? The problem was that tools like RubyGems.org or Bundix that use the gemspec as the source of truth for dependencies didn't pick up on the development dependency on Rubocop. ### What was your diagnosis of the problem? My diagnosis was that the reason for this, which was that Rubocop had a minimum Ruby version of 2.0.0, was no longer an issue, since Bundler 2 doesn't support Rubies that old anyway. ### What is your fix for the problem, implemented in this PR? My fix was to move the Rubocop requirement into the gemspec. ### Why did you choose this fix out of the possible options? I chose this fix because it addresses the problem I was having, feels right, and the old workaround doesn't look like it's necessary any more. Co-authored-by: Alyssa Ross <hi@alyssa.is>
| * Move Rubocop development dependency into gemspecAlyssa Ross2019-01-231-0/+1
| | | | | | | | | | | | | | | | | | Now that Bundler no longer supports Ruby <2.3, the Ruby minimum version requirement that prevented Rubocop from being specified as a development dependency in the gemspec no longer applies. Having Rubocop in the gemspec is useful for tools like RubyGems.org or Bundix that use it as the source of truth for dependencies.
* | Bump rake version of Bundler's dependency.SHIBATA Hiroshi2019-01-231-1/+1
|/ | | | Ruby 2.7.0-dev added the warnings about Object =~. We need to avoid it.
* embed Shellwords.escape into bundler gemspecColby Swandale2018-12-291-1/+2
|
* fix usuage of IO.popen on Ruby 1.8Colby Swandale2018-12-281-1/+1
|
* Fix specs that are broken in ruby 2.6Samuel Giddins2018-12-281-3/+1
|
* Revert File.file? conditioon on gemspec, Because it break ↵support-structure-of-ruby-coreSHIBATA Hiroshi2018-11-071-4/+4
| | | | spec/runtime/setup_spec.rb:896
* expand version path for rspec examples.SHIBATA Hiroshi2018-11-071-3/+2
|
* Added extnameSHIBATA Hiroshi2018-11-071-2/+2
|
* To use File.file? instead of handling LoadError.SHIBATA Hiroshi2018-11-061-3/+4
|
* Support file structure of ruby core repository.SHIBATA Hiroshi2018-10-201-1/+7
|
* http://bundler.io redirects to https://Akira Matsuda2018-10-031-1/+1
|
* GitHub is HTTPS by defaultAkira Matsuda2018-10-031-2/+2
|
* add Stephanie Morillo to gemspec author listcolby/invite-stephanie-morilloColby Swandale2018-08-231-1/+1
|
* Add new team members to gemspec authorsindirect/update-authorsAndre Arko2018-08-141-2/+3
|
* add the new team members of the bundler core team to the author list in the ↵colby/update-bundler-authorsColby Swandale2018-01-181-1/+1
| | | | Bundler gemspec
* Include bundler.gemspec in the gem because warbler breaks w/o itDaniel Ritz2017-11-301-0/+2
| | | | f06405 caused a regression with warbler, described in #6165
* [gemspec] Ensure we don’t activate the default gem under Ruby 2.5Samuel Giddins2017-10-221-3/+1
| | | | This will keep the (development) binstubs working
* Pass gemspec directory path to GitPatricia Arbona2017-09-281-1/+3
|
* [Gemspec] Set 2.0 required ruby/rubygems versionsSamuel Giddins2017-08-171-2/+7
|
* Auto merge of #5862 - NickLaMuro:remove_bin_dir_from_gem_build, r=indirectThe Bundler Bot2017-08-151-1/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove uneeded files packaged into bunder's gem build on rubygems What was the end-user problem that led to this PR? -------------------------------------------------- I noticed while doing a `bundle open bundler` (inception!) that we have included the `bin/` directory in the packaged gem. While this is not hurting anything, it provides a bunch of scripts that won't function properly in any capacity when installed through ruby gems. While doing that, I noticed that the dotfiles for CI were also packaged up in the gem, so I made sure to only include specific files from there that seemed to provide value when being shipped as a gem. What is your fix for the problem, implemented in this PR? --------------------------------------------------------- Change the reduction of the results from `git ls-files` to be a whitelist instead of a blacklist. This was to reduce the complexity of the regexp that would have resulted from change what directories to include, not ship CI files in the top level dir, while also still wanting to ship the `CHANGELOG.md`, `LICENSE.md`, and `README.md` files along with the build, since I think they do provide value being included with the packaged gem. Why did you choose this fix out of the possible options? -------------------------------------------------------- Some of the choices here were a bit subjective, especially what I decided on as "necessary" regarding the `.md` files that I included. Projects like rails went with these three, so I decided to use that as a base, but some might think that the `CHANGELOG.md` being included is a bit excessive and is a large file that most won't even read in this form, and I don't have a hard opinion one way or the other. That said, I do think that developer files should not be packaged in the gem, and this precedent has already been set with the original blacklist, it just wasn't very complete. How I did it could probably be changed based on developer preference, but I tried to stay as true to what was already there before all else.
| * Include the READMEish files in the buildNick LaMuro2017-07-121-0/+2
| | | | | | | | | | | | While not required for the build to function, they provide links and information to developers who find themselves in the codebase of the gem they have installed on their system.
| * Only include the bin and lib directories from gitNick LaMuro2017-07-121-1/+1
| | | | | | | | | | | | | | The `bin/` dir was getting included as part of the bundler release, along with all of the files from the top level directory in the project, most of which don't need to be there (CI config files mostly). Only the `lib/` and `exe/` dirs are needed from git.
* | [RuboCop] Enable Layout/EmptyLineAfterMagicComment copKoichi ITO2017-07-161-0/+1
|/
* Avoid warnings in the specs on Ruby 1.8.7seg-spec-warningsSamuel Giddins2017-06-201-1/+1
|
* [RuboCop] Enable Style/PercentLiteralDelimitersKoichi ITO2017-05-281-1/+1
| | | | Run `rubocop -a --only Style/PercentLiteralDelimiters` and `rubocop --auto-gen-config`.
* add metadata to gemspecdwr-metadataDavid Radcliffe2017-04-241-0/+9
| | | | Including new changelog link
* wrap at 80 charsaa-core-team-alumniAndre Arko2017-02-181-1/+5
|
* Add core team alumni to the gemspec authorsAndre Arko2017-02-181-1/+1
|
* remove post-install on account of confusionaa-rm-post-installAndre Arko2017-02-151-7/+0
| | | | | | as demonstrated on twitter[1], this message was unfortunately convincing people that Ruby Together pays for the rubygems.org servers. let's remove it and come up with something clearer later. [1]: https://twitter.com/MelissaKaulfuss/status/829504864229023744
* add improvingimprove-messagingAndre Arko2017-02-011-4/+4
|
* marketing-ify the post-install messageAndre Arko2017-02-011-4/+4
|
* update link, appeal to better naturesaa-update-appealAndre Arko2017-01-091-3/+3
|
View Lorry Controller Status