Improve visibility and control over image publishing process

[nquinquenel]

While the current image publishing process is simple - since most tasks are handled on your side - it also lacks transparency. As a result, we have limited insight and control over how and when our image is published.

Currently, the process feels somewhat opaque:

• We don’t know when updates are triggered or completed.
• We have no way to manually trigger a publish/update.
• If a problem occurs on our MCP server (e.g., tools list fails to load), we’re not notified.
• The calculation behind the Docker Scout Health Score is unclear.

For example, we recently released a new version, but our image was not updated for over a week - and we had no visibility into the reason or how to expedite it.

Could we have more visibility into the publishing pipeline (e.g., status, logs), or introduce a way to manually trigger or retry an image update?

Also, could you provide documentation or metrics around the Docker Scout Health Score computation?

Thanks for your help!

[nquinquenel]

I just noticed the PRs titled chore: update pin for <server>. I’m not sure if that’s a recent addition, but it’s already quite helpful for understanding the root cause of failures! I also briefly looked at the update-pins.yaml workflow, but it appears that this workflow is triggered manually.