v1.69.5

EvoMap/evolverv1.69.5Apr 21, 2026by autogame-17

AI Summary

Bug fix release addressing a regression where hub-issued 16-hex node_ids were silently rejected, causing the client to regenerate new node_ids from a device-fingerprint fallback on each restart. The validator now accepts 12-32 hex chars to match actual hub-issued formats.

Key Highlights

Fixed regression where 16-hex node_ids from hub were silently rejected
Persisted-node_id validator now accepts 12-32 hex chars matching hub-issued formats
A2A_NODE_ID env values with unexpected formats now emit clear warning pointing to evomap.ai
Users with overwritten node_id need to re-claim via A2A_NODE_ID or evomap.ai

New Features

Expanded node_id validator to accept 12-32 hex characters
Warning system for A2A_NODE_ID environment variable format validation

Full Release Notes

## v1.69.5 - node_id format fix

Fixes a regression where hub-issued 16-hex node_ids (e.g. `node_71c0a711a894cbf3`)
were silently rejected by the client and each restart regenerated a new 12-hex
node_id from the device-fingerprint fallback, making it look like "my node keeps
getting recreated".

**What changed**

- The persisted-node_id validator now accepts 12-32 hex chars, matching what the
  hub actually issues
- `A2A_NODE_ID` env values with unexpected formats are still used as-is but now
  emit a clear warning pointing to https://evomap.ai

**Upgrading**

If you set `A2A_NODE_ID` to a 16-hex hub-issued id, or copied one into
`~/.evomap/node_id`, upgrade to v1.69.5. If your `~/.evomap/node_id` was already
overwritten by the fallback, either:

- set `A2A_NODE_ID=<your hub node_id>` in your shell, or
- delete `~/.evomap/node_id` and re-claim your original node on evomap.ai

Internal improvements and stability enhancements.