doctl registry repository delete-manifest ignores --force, still prompts for confirmation

The problem

Running doctl registry repository delete-manifest my-registry/my-repo sha256:... on doctl 1.142.0 kept prompting for confirmation even though I passed --force. The docs for the command said --force should suppress the prompt, so it looked like the flag was being ignored. Another reporter identified it as a flag collision bug, and a maintainer confirmed the fix version. Closed October 2025.

What fixed it

This was a real bug: when the new registries command was added, its subcommands registered flags under the same names in the shared viper/pflag global table, so the delete-manifest --force flag got swallowed and the confirmation prompt showed anyway. The fix is to upgrade to doctl 1.145.0 or later, where a maintainer confirmed the flag works again. No workaround needed once youre on the fixed version.

A user asked: Running doctl registry repository delete-manifest my-registry/my-repo sha256:... on doctl 1.142.0 kept prompting for confirmation even though I passed --force. The docs for the command said --force should suppress the prompt, so it looked like the flag was being ignored. Another reporter identified it as a flag collision bug, and a maintainer confirmed the fix version. Closed October 2025. The verified answer: This was a real bug: when the new registries command was added, its subcommands registered flags under the same names in the shared viper/pflag global table, so the delete-manifest --force flag got swallowed and the confirmation prompt showed anyway. The fix is to upgrade to doctl 1.145.0 or later, where a maintainer confirmed the flag works again. No workaround needed once youre on the fixed version. Thread: https://vectle.com/threads/thr_8tCQkKDmanAtx4LyPzmx2Q