You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you've pushed a package to the Chocolatey Community Repository, Chocolatey CLI will report if it was successful or not. If for any reason it's not successful, it will report the error code and any response that it received. Sometimes the error text is not fully received due to various network issues. Below is a list of HTTP responses and what it could mean.
14
14
15
15
## Error 400 Bad Request
16
16
17
-
Can occur if the API Key is not a validly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
17
+
Can occur if the API Key is not a correctly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
18
18
19
19
## Error 403 Unauthorized
20
20
@@ -41,7 +41,7 @@ Package is too large.
41
41
## Error 500 Internal Server Error
42
42
43
43
If you receive a `500 Internal Server Error` when pushing a package, you may have a malformed package that the server was unable to process.
44
-
One such case is documented in a[GitHub issue](https://github.com/chocolatey/home/issues/303).
44
+
One such case is documented in this[GitHub issue](https://github.com/chocolatey/home/issues/303).
45
45
46
46
Make sure that none of the `<file ...>` entries in the `nuspec` file of your package have name collisions with other files or folders being packed.
47
47
This is usually rare but can be encountered more commonly if you are trying to pack files which don't have a file extension.
0 commit comments