Errors

conflict

The registry refused the release with a conflict or rate-limit response; wait and try again.


Kind	`disko` command error
`disko` exit code	5 (conflict)

disko publish reports conflict when the registry answers 409 or 429 without a more specific error code, and disko dev when disko-master answers that way to creating a test room. When the service does send its own code, disko reports that code instead, so conflict itself only appears as a fallback. The command exits with code 5. The more common conflicts have their own pages: version_exists and quota_exceeded.

json

{
  "ok": false,
  "command": "publish",
  "error": "conflict",
  "message": "the registry refused the release (429 conflict); wait and try again",
  "docs": "https://docs.disko.ooo/errors/conflict"
}

Fix

Wait a moment and run the command again. A failed publish never uses up the version, and publishing the identical archive again is a safe retry. If disko dev keeps being refused, check the Creator Portal: it may ask you to complete your account profile first.