0.7.1

Fix cache lookup when parallel jobs populate the same Docker image cache.

The post step now uses the same archive path for lookup, restore, and save. Previously, its lookup could miss a cache created by another job because it calculated a different cache version. Both committed action bundles include the fix.

Inputs, outputs, production dependencies, the cache format, and the Node.js 24 runtime are unchanged from 0.7.0.

Validation:

• All 16 tests across six suites pass, with 100% production-code coverage and a regression that fails with the previous lookup.
• Two local bundle builds are identical; CI rebuilds and verifies the committed bundles.
• Real GitHub Actions cache save/restore passes on Ubuntu 22.04, Ubuntu 24.04, and Windows 2025.
• The full hosted Test workflow passes on both the release PR and the exact tagged main commit.

The README now clarifies whole-image caching, runner requirements, and fork attribution. Contributor and security guidance are included; inherited Slack automation has been removed.

Upgrade using the immutable commit pin:

- uses: AndreKurait/docker-cache@e1eb0120c0c16b3f1c6ff1c0ef4ebc9f67f8dc6a # 0.7.1
  with:
    key: docker-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('compose.yaml') }}

Place the step after checkout and before pulling or building images. Replace compose.yaml with the files that determine your images. You can also use AndreKurait/docker-cache@0.7.1.

The existing 0.7.0 tag is unchanged. Workflows pinned to that tag or its commit need to update their action reference to receive this fix.

Changes: #3 and #4.