---
digest: >
  Mirror Mind v0.10.2 fixes stale welcome release awareness when stable advances
  again inside the welcome cache window. A clone behind stable should see the
  latest available version, not an intermediate version cached a few minutes
  earlier. This patch keeps healthy up-to-date cache behavior cheap while making
  visible update notices refresh before they are shown.
---

# v0.10.2 — Fresh Release Awareness

**Date:** 2026-05-25

## Highlights

- Welcome update notices refresh even inside the cache TTL when an update is
  already visible.
- Users behind stable now see the latest stable tag after the stable branch
  advances again.
- `up_to_date` cache entries still respect the TTL to avoid unnecessary remote
  checks.
- Regression coverage now verifies that a cached `v0.10.0` notice refreshes to
  `v0.10.1` when remote stable has advanced.

## Where We Started

After publishing v0.10.1, production validation showed the welcome still saying
`v0.10.0` was available even though `origin/stable` and the `v0.10.1` tag already
pointed to the newer release. The cache was technically fresh, but semantically
stale: it preserved an intermediate update notice after stable moved again.

## What Changed

The welcome now treats visible update notices differently from healthy
up-to-date cache entries. If the cache says `update_available`, Mirror refreshes
release awareness before rendering the welcome, even when the cache is still
inside its normal TTL. If the cache says `up_to_date`, the TTL behavior remains
unchanged.

This means a user can leave a production clone on an older version, publish a
new patch shortly afterward, and still see the newest available release without
manually deleting `runtime/update-check.json`.

## Conscious Exclusions

This patch does not implement cumulative release notes across all versions
between the installed version and latest stable. It only ensures the visible
latest-version signal is fresh.

It also does not change `runtime update --check`, which remains intentionally
conservative and does not fetch release-note files.

## What We Learned

A cache can be fresh by time and stale by meaning. For a status that is already
asking the user to act, correctness matters more than avoiding one lightweight
remote check. The cheap path is still correct for `up_to_date`; the action path
must be more vigilant.

## Next Horizon

The next improvement is cumulative release awareness: when a user asks `what
changed?`, Mirror should be able to show all release notes between the installed
version and the latest stable version, not only the latest release note.
