doobidoo/mcp-memory-service v10.70.3

v10.70.3 - fix(ci): multi-arch-safe GHCR cleanup

on GitHub

fix(ci): multi-arch-safe GHCR cleanup

Resolves the docker pull 404 that has affected all multi-arch tags since v10.66.

Root Cause (diagnosed by @jonatanbellido, issue #1044)

The cleanup-images.yml workflow used actions/delete-package-versions triggered via workflow_run after each release. This action deleted untagged GHCR packages — which included the per-platform child manifests (e.g. linux/amd64, linux/arm64) that are children of the multi-arch index manifest. Those child manifests are intentionally untagged by design; deleting them broke the multi-arch index, causing 404s on every docker pull.

Fix (PR #1052)

• Replaced actions/delete-package-versions with dataaxiom/ghcr-cleanup-action, which correctly identifies and skips manifests that are referenced by a multi-arch index
• Removed the workflow_run-after-release trigger that was racing the publish job

What this release does

This patch re-publishes fresh platform manifests via the normal Publish and Test (Tags) CI pipeline. Because the cleanup workflow is now multi-arch-safe, these manifests will survive cleanup and docker pull ghcr.io/doobidoo/mcp-memory-service:v10.70.3 (and :latest) will work correctly.

Changelog

See CHANGELOG.md for full details.

Docker users: After the publish workflow completes (~5 min), docker pull ghcr.io/doobidoo/mcp-memory-service:latest should work again. The PyPI package at this version is also available.