Today I tried to publish my first package. Here's what happened:
$ elm-package publish
Verifying gampleman/elm-visualization 1.0.0 ...
This package has never been published before. Here's how things work:
* Versions all have exactly three parts: MAJOR.MINOR.PATCH
* All packages start with initial version 1.0.0
* Versions are incremented based on how the API changes:
PATCH - the API is the same, no risk of breaking code
MINOR - values have been added, existing values are unchanged
MAJOR - existing values have been changed or removed
* I will bump versions for you, automatically enforcing these rules
The version number in elm-package.json is correct so you are all set!
Error: The following HTTP request failed.
<https://api.github.com/repos/gampleman/elm-visualization/tags>
{"message":"API rate limit exceeded for 87.246.78.46. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}
I haven't been doing anything much with Github, except fairly normal usage, so I suspect it might have to do with shared IP addresses (although that's just my guess).
This repeated for a couple of hours until finally I managed to publish my package.
I was wondering if we could add a way to (optionally) authenticate the requests, so that the process could be unblocked.
Today I tried to publish my first package. Here's what happened:
I haven't been doing anything much with Github, except fairly normal usage, so I suspect it might have to do with shared IP addresses (although that's just my guess).
This repeated for a couple of hours until finally I managed to publish my package.
I was wondering if we could add a way to (optionally) authenticate the requests, so that the process could be unblocked.