registry repository list-v2 ignores --format and --no-header flags

[silvercondor]

Describe the Issue:

The --format and --no-header flags are completely ignored by doctl registry repository list-v2. The command outputs all columns with headers regardless of the format specified.

Steps to reproduce:

# Expected: Only repository names, no header
doctl registry repository list-v2 --format Name --no-header

# Actual output: Full table with all columns and header
Name                       Latest Manifest                                                            Latest Tag    Tag Count    Manifest Count    Updated At
my-app-prod                sha256:a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2    latest        2            3                 2025-12-04 06:57:34 +0000 UTC
my-app-stg                 sha256:f6e5d4c3b2a1f6e5d4c3b2a1f6e5d4c3b2a1f6e5d4c3b2a1f6e5d4c3b2a1f6e5    latest        3            5                 2025-12-11 18:35:05 +0000 UTC

Expected behavior:

doctl registry repository list-v2 --format Name --no-header
# Should output:
my-app-prod
my-app-stg
...

Workaround:

Using --output json with jq works correctly:

doctl registry repository list-v2 --output json | jq -r '.[].name'

Environment:

• doctl version: 1.148.0 (also reproduced on 1.141.0 in CI)
• OS: Ubuntu 22.04 / Ubuntu 24.04 (GitHub Actions)
• Installation method: GitHub Actions digitalocean/action-doctl@v2

Additional Details:

The same issue affects doctl registry repository list (non-v2). This breaks scripts that rely on grep -Fxq for exact matching since the full row is returned instead of just the name.

Additional Note: We noticed this issue started to happen since December 27th

[timofey-drozhzhin]

Can confirm. It would be nice to include tests to prevent this in the future.

[lohitkolluri]

Opened #1851 — list-v2 was registering the v1 Repository displayer instead of RepositoryV2, which caused --format / --no-header to be ignored for scripted output.

[ds5678]

I am seeing similar behavior for doctl registry repository list-manifests.

[lohitkolluri]

Thanks for flagging this, @ds5678.

#1851 fixed list-v2 (and registries repository list-v2), where the command was registering the v1 Repository displayer instead of RepositoryV2, causing --format and --no-header to be ignored in scripted output.

For list-manifests, the command already registers RepositoryManifest for both:

• registry repository list-manifests
• registries repository list-manifests

so this may be a separate issue.

Could you share:

• doctl version
• the exact command you ran (including --format / --no-header)
• a short snippet of the actual vs expected output

That’ll help confirm whether this is the same root cause or something different. If it reproduces, I can follow up with a fix and regression test similar to #1851 .

[ds5678]

doctl version: v1.160.0

doctl auth init -t "${{ secrets.DO_API_TOKEN }}"
doctl registry repository list-manifests "${{ vars.REGISTRY_IMAGE_NAME }}" --format Digest,UpdatedAt --no-header | sort -rk2

Using token for context default

Validating token... ✔
Manifest Digest                                                            Compressed Size    Uncompressed Size    Updated At                       Tags
sha256:9684f37257f28a48d87ca013554a8368a3180998435803ea09a953cb45cf3870    92.25 MB           222.13 MB            2025-03-10 06:26:01 +0000 UTC    [8af5db2537a97d06f747e67991e0fa776077e14e]
sha256:4f5b2739a5fd2ff4b9e5d7f5d304b21997e706c6983a62744fb7c8124f5aea9d    92.22 MB           222.12 MB            2026-05-28 15:28:21 +0000 UTC    [ed88cdd8f68998b97abad2b4fb599e260ef6db68]
sha256:6b84c259dc55c0c1d5e98c84d23b8f1672f207cc0650d523477812e28aad3ba6    92.09 MB           221.43 MB            2024-12-23 17:05:44 +0000 UTC    [ea32e3f4b7991db821c3ea8b345278cdb68fa48d]
sha256:60d27ec050763c43ea6f72975c5fba96884603f66f0f9e763c88153783b71ac5    56.94 MB           146.62 MB            2026-05-28 16:37:23 +0000 UTC    [99e4e8957835ed597f469e2ddc8dea96b9c3d099]
sha256:ac29cb2a0797a9728d65ed335b67fed5b2dd590f4450b0eff0a4b0faf6ecfe05    56.64 MB           146.55 MB            2026-05-28 16:50:34 +0000 UTC    [latest 412282fd27a5616a000e7a45b7b9c8827a0b68c7]

[ds5678]

Expected output:

Using token for context default

Validating token... ✔
sha256:f1ca831c969c0dc5844268bbb3cc8c4318ae2de9240b783fdb1343a4aae5ec56    2026-05-28 18:33:13 +0000 UTC
sha256:d3c39a42d6b2f49b21953821e95a2afa40c327b2cbb51ebdaa020347a23baa15    2026-05-28 18:27:59 +0000 UTC
sha256:c83ccd17879222386b1af55fe8e9d8f48630bb42602364ec02e3c6c117ebff9c    2026-05-28 18:23:41 +0000 UTC
sha256:88f95b61db5a816ccc42083fefd99df26761d6e420e0f99b8ba39418a3891585    2026-05-28 18:13:48 +0000 UTC
sha256:aa05fb3658aee710b952eb1e3175fca1db382281e86f34021dcab00a5c33ba1b    2026-05-28 18:09:15 +0000 UTC
sha256:64b2b527927f3e7769b470cdeb6bdcc0ee47a2d5361cbd8e40a016ccd71a9bef    2026-05-28 18:04:27 +0000 UTC

I did a binary search and narrowed my issue to between 1.141.0 and 1.142.0.

v1.141.0...v1.142.0