Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a placeholder
dependabot-core.gemspec
(dependabot#7171)
While auditing [our gems](https://rubygems.org/profiles/dependabot), I noticed there was a `dependabot-core` gem that hadn't been updated in years: https://rubygems.org/gems/dependabot-core/versions/0.94.13 This was probably the original gem before it was all split apart into the meta gem `dependabot-omnibus` and the subgems. This creates confusion because the name matches the `dependabot-core` repo. At first I planned to delete it, but then I saw the note on Rubygems that deleting a gem frees up the namespace. We would much rather own this namespace to prevent namesquatting, so I've created a placeholder gemspec that has no associated source code. I wasn't sure if `gem` would allow building/publishing with no source code, so tested, and it all worked: ```shell $ gem build dependabot-core.gemspec WARNING: no files specified WARNING: description and summary are identical WARNING: See https://guides.rubygems.org/specification-reference/ for help Successfully built RubyGem Name: dependabot-core Version: 0.95.1 File: dependabot-core-0.95.1.gem $ gem push dependabot-core-0.95.1.gem Pushing gem to https://rubygems.org... Successfully registered gem: dependabot-core (0.95.1) ``` You can see the updated gem here: https://rubygems.org/gems/dependabot-core/versions/0.95.1 Which is much less confusing than it used to be. I think we should keep the gemspec around in case anyone needs to make small changes at some point, no need for them to recreate the whole file. This repo seemed like the best fit, I wasn't sure whether to float it in `./common`, so I stuck it in the root dir... seems harmless enough.
- Loading branch information