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.

Sign up for GitHub

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

Jump to bottom

Yank a private gem #17

Closed

smellsblue opened this issue Oct 6, 2015 · 0 comments · Fixed by #36

Contributor

smellsblue commented Oct 6, 2015

Yank private gems.

Since rubygems doesn't support yanking a host other than www.rubygems.org, we should add a temporary Thor task to make it easy.

The task should be clearly marked as temporary.

Here are my thoughts for behavior, please comment if it should differ:

Yanked gem files will remain, in case of unyank
Fetching gem version will result in 404
Mark in database as yanked, and don't return in dependencies API

smellsblue mentioned this issue

Yanking gems #36

Merged

smellsblue closed this as completed in #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment