Skip to content

release: 0.9.0-beta.154 — API key on remaining keyless Skaldleita call sites (#264)#267

Merged
deucebucket merged 2 commits into
mainfrom
develop
Jul 14, 2026
Merged

release: 0.9.0-beta.154 — API key on remaining keyless Skaldleita call sites (#264)#267
deucebucket merged 2 commits into
mainfrom
develop

Conversation

@deucebucket

Copy link
Copy Markdown
Owner

Promotes the single commit merged to develop since beta.153: the #264 completion (PR #266).

Four call sites (api_book_detail, api_author_detail, api_series_detail, identify_ebook_from_filename) now attach get_signed_headers() + X-API-Key like all sibling code, instead of sending keyless requests that guaranteed 401s against Skaldleita's key-or-401 gate.

Verification (already performed on the PR #266 audit)

  • test-env suites: 290/290 + 10/10, independently re-run
  • ruff F821: clean
  • Line-by-line diff review; APP_VERSION bumped to 0.9.0-beta.154 to match CHANGELOG
  • No unrelated changes: develop→main delta is exactly this fix

Merging closes #264.

Clawd and others added 2 commits July 14, 2026 05:08
…eita call sites

api_book_detail, api_author_detail, api_series_detail, and
identify_ebook_from_filename still called the Skaldleita API with no
headers, guaranteeing 401s against the key-or-401 gate. Each now
resolves the API key the same way sibling code does (config /
load_secrets with BOOKDB_PUBLIC_KEY fallback) and sends
get_signed_headers() + X-API-Key. Version bumped to 0.9.0-beta.154.
…lers

fix: Attach API key to remaining keyless Skaldleita call sites (#264)
@deucebucket
deucebucket merged commit 6c254fc into main Jul 14, 2026
8 checks passed
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.

API key not attached on all requests → keyless 401 loop (auto-inject works on develop, stuck behind release + 3 stragglers)

1 participant