_⚠️ Potential issue_ | _🟠 Major_

[kannon92]

⚠️ Potential issue | 🟠 Major

Remove trailing whitespace from the image pull spec.

Line 8 ends with a space inside the JSON string, so the stored image reference is not exact and may fail in strict parsers/consumers. Please trim the value (and ideally normalize other image entries in this file the same way).

Proposed fix

-    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-must-gather-main@sha256:89656a2c023a2e94d3b5faa8f41fee92f8fb9ab6a31cc820292067273721738b "
+    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-must-gather-main@sha256:89656a2c023a2e94d3b5faa8f41fee92f8fb9ab6a31cc820292067273721738b"

As per coding guidelines, "Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity."

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-must-gather-main@sha256:89656a2c023a2e94d3b5faa8f41fee92f8fb9ab6a31cc820292067273721738b"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@related_images.developer.json` at line 8, The JSON entry for the "image" key
contains a trailing space in the pull spec
("quay.io/...@sha256:89656a2c023a2e94d3b5faa8f41fee92f8fb9ab6a31cc820292067273721738b
") which can break strict parsers; trim the trailing whitespace from that string
and scan the file for other "image" values to normalize/remove any
leading/trailing whitespace so all image pull specs are exact.

Originally posted by @coderabbitai[bot] in #1717 (comment)

[kannon92]

Note this is harmless but it does look weird so going to fix it to avoid future noise from coderabbit

[openshift-ci]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-ci]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale