Don't include development dependencies in info files #24
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.
What was the end-user or developer problem that led to this PR?
#22 -- clients are forced to download (and resolve) development dependencies of gems served with these indexes.
What is your fix for the problem, implemented in this PR?
Filter out development dependencies in the info file. I noticed that this is what RubyGems.org does, for example: https://rubygems.org/info/graphql (doesn't have development_dependencies)
Make sure the following tasks are checked
I noticed that some tests on master are already failing on
rubygems:> 1.3.1
-- I didn't attempt to fix those.