ThinkWatch v1.0.1

Images

• ghcr.io/thinkwatchproject/think-watch-server:1.0.1
• ghcr.io/thinkwatchproject/think-watch-web:1.0.1

Helm

helm install think-watch ./think-watch-1.0.1.tgz \
  --namespace thinkwatch --create-namespace

---

Release-pipeline validation. No product change — the published
binary, REST surface, MCP wire shapes, and audit semantics are
identical to v1.0.0. Operators pinning 1.0.0 have no reason to
bump; those tracking :latest move forward.

Changed

• Release workflow — arm64 image builds now run on a native
  arm64 runner (ubuntu-24.04-arm) instead of QEMU emulation.
  v1.0.0's server image build took 1h24m; this should drop to
  ~10 min. Multi-arch manifest assembled by a new merge job via
  docker buildx imagetools create.
• Node 24 opt-in — workflow sets
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true so all actions/* +
  docker/* run on Node 24 ahead of GitHub's 2026-06-02 forced
  cutover.

ThinkWatch v1.0.0

Images

• ghcr.io/thinkwatchproject/think-watch-server:1.0.0
• ghcr.io/thinkwatchproject/think-watch-web:1.0.0

Helm

helm install think-watch ./think-watch-1.0.0.tgz \
  --namespace thinkwatch --create-namespace

---

Stability commitment. No code delta since 0.5.0 — this tag marks
the point at which the API surface becomes a SemVer
commitment.

Changed

• Versioning policy — from this tag onwards every breaking
  change (REST routes, MCP wire shapes, audit-row JSON keys,
  database schema, public Rust APIs in published crates) requires
  a major bump. Operators chasing the :latest tag on the GHCR
  images can do so without surprise.

Notes

• Docker images cut at this tag receive :latest for the first
  time — the release workflow suppresses :latest on 0.x and
  pre-release tags. Pin the version in production rather than
  tracking :latest unless you have a controlled rollback path.