release-docker workflow failed

[github-actions]

The release-docker workflow failed for version v1.8.1.

Run: https://github.com/z4jdev/z4j/actions/runs/30531148593

The public version tag is promoted only after signing and attestation.
Inspect the failed gate, fix it, and rerun the same release tag.

[github-actions]

The release-docker workflow failed for version v1.9.0.

Run: https://github.com/z4jdev/z4j/actions/runs/32913853102

This workflow creates only a qualified digest and never mutates public release tags.
Inspect the retained signed receipt before retrying or dispatching promotion.
If the version tag already points at different bytes, publish repaired bytes under a new version.

[github-actions]

The release-docker workflow failed for version v1.9.1.

Run: https://github.com/z4jdev/z4j/actions/runs/33046344848

This workflow creates only a qualified digest and never mutates public release tags.
Inspect the retained signed receipt before retrying or dispatching promotion.
If the version tag already points at different bytes, publish repaired bytes under a new version.

[github-actions]

The release-docker workflow failed for version v1.10.0.

Run: https://github.com/z4jdev/z4j/actions/runs/33274939771

This workflow creates only a qualified digest and never mutates public release tags.
Inspect the retained signed receipt before retrying or dispatching promotion.
If the version tag already points at different bytes, publish repaired bytes under a new version.

[github-actions]

The release-docker workflow failed for version v1.11.0.

Run: https://github.com/z4jdev/z4j/actions/runs/34537163349

This workflow creates only a qualified digest and never mutates public release tags.
Inspect the retained signed receipt before retrying or dispatching promotion.
If the version tag already points at different bytes, publish repaired bytes under a new version.