Skip to content
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.

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

Update top-level docs to the next-to-last version if the last version is being reverted #383

Closed
ericmj opened this issue Jul 14, 2016 · 3 comments

Comments

@ericmj
Copy link
Member

ericmj commented Jul 14, 2016

No description provided.

@idyll
Copy link

idyll commented Sep 1, 2016

Can this include a flag or indication of the nature of the issue with the previous package.

I am hoping to use this to add additional scanning beyond just out of date and instead fail builds when a package you are using contains a known security issue.

@ericmj
Copy link
Member Author

ericmj commented Sep 1, 2016

This is only for docs. You can only revert packages for up to one hour after its initial release so it's unlikely that's for security reasons.

@ericmj
Copy link
Member Author

ericmj commented Jun 2, 2018

This will not be needed when we move to the new hexdocs service.

@ericmj ericmj closed this as completed Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants