Skip to content

[11/15] Docs: add the v5.1-to-v5.2 migration guide - #164

Open
UnknownJoe796 wants to merge 1 commit into
version-5.3from
v53/docs-migration-v52
Open

[11/15] Docs: add the v5.1-to-v5.2 migration guide#164
UnknownJoe796 wants to merge 1 commit into
version-5.3from
v53/docs-migration-v52

Conversation

@UnknownJoe796

Copy link
Copy Markdown
Contributor

Adds the v5.1-to-v5.2 migration guide. Documentation only.

@UnknownJoe796
UnknownJoe796 force-pushed the v53/auth-normalization branch from 1af4070 to afcde3e Compare July 29, 2026 22:54
@UnknownJoe796
UnknownJoe796 force-pushed the v53/docs-migration-v52 branch from ec8b005 to d2fd0af Compare July 29, 2026 22:54
Covers the complete set of changes to move a consumer from 5.1.x to
5.2.0, all verified against a real downstream app (USBE) that then ran
locally and served its KiteUI web client unchanged:

- Bump service-abstractions to the version 5.2 was built against
  (1.2.0-1-b2f7bd67); a mismatch compiles but throws NoSuchMethodError
  at runtime (SettingContext.getOpenTelemetry()).
- New required AuthEndpoints/SessionManager `cache` parameter.
- Telemetry moved from OpenTelemetrySettings to TelemetryBackend.Settings
  (both the code setting and the settings.json `"telemetry"` entry, which
  was previously `null`).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uur4dHcoa1a259iiTzvin3
(cherry picked from commit 84978bc)
(cherry picked from commit d2fd0af)
@UnknownJoe796
UnknownJoe796 force-pushed the v53/auth-normalization branch from afcde3e to a123e57 Compare July 30, 2026 02:19
@UnknownJoe796
UnknownJoe796 force-pushed the v53/docs-migration-v52 branch from d2fd0af to faf3fc9 Compare July 30, 2026 02:20
@UnknownJoe796
UnknownJoe796 changed the base branch from v53/auth-normalization to version-5.3 July 30, 2026 02:24
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