# v3.13.1

1 commit since v3.13.0: 1 fix. A bug fix only, so patch.

## Read this before upgrading

Nothing changes unasked. The fix only affects instances that have
`clientRxCoverage` enabled and receive data from CoreDrive RX companions.

What it does not do: node-discover replies received before this release are
not recovered. `client_rx_observations` keeps no raw bytes, so the responder's
pubkey is gone. Coverage from discover replies starts at the upgrade.

## Fixes

- **Node-discover replies count as coverage** (#2111). A CoreDrive RX companion
  that runs node-discover hears each repeater that answers, at zero hops, and
  the reply carries the repeater's own pubkey. The ingestor dropped these
  replies from `client_receptions`, so a companion could log dozens of replies
  and the coverage page showed nothing for it. Reported by an operator on
  v3.13.0: 32 discover replies in 16 minutes, 0 coverage rows. On a deployment
  that has had this fix since August, discover replies are 4,232 of 9,723
  coverage rows over 7 days (44%). The server now also matches the 8-byte
  prefix those replies carry, so the rows show up in a node's own coverage.

## Issues closed

None. The report came in through Discord, not as a GitHub issue.

## Contributors

Pull request authors: @efiten (1).

No co-authors other than tooling are credited in the commits.

## Upgrade notes

No manual migration step, no new table, no configuration key added or changed.