Skip to content

0.7.0: entries_to_refresh() / resolve_entry(); feedback takes cache_entry_id - #8

Merged
imxinchengyou merged 1 commit into
mainfrom
feat/entries-to-refresh
Oct 31, 2026
Merged

imxinchengyou merged 1 commit into
mainfrom
feat/entries-to-refresh

Conversation

@imxinchengyou

Copy link
Copy Markdown
Owner

Why

This is the client for cacheverifier-service's new "Entries to refresh" feature: cache entries the tenant's feedback reported stale, or wrong more often than right.

Changes

  • CacheVerifier.entries_to_refresh(): GET /v1/monitor/entries-to-refresh.
  • CacheVerifier.resolve_entry(key): POST /v1/monitor/entries-to-refresh/{key}/resolve.
  • feedback(cache_entry_id=...): on both CacheVerifier and LocalVerifier. It's the caller's own cache key, which the list hands back.
  • Version: 0.7.0, with a CHANGELOG entry and a README section plus API-table rows.

Testing

  • New test_entries_to_refresh_round_trip: feedback sends cache_entry_id; the list and resolve calls hit the right paths.
  • cache_entry_id omitted when unset: this is now asserted.
  • Suite: 56 passed, 1 skipped. ruff and mypy are clean.

Release

Release after cacheverifier-service's entries-to-refresh PR is deployed: create the GitHub Release v0.7.0.

@imxinchengyou
imxinchengyou merged commit 63c8b01 into main Oct 31, 2026
7 checks passed
@imxinchengyou
imxinchengyou deleted the feat/entries-to-refresh branch October 31, 2026 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant