refactor(remote-config): Migrate config to opaque-manifest wire format#3641
Merged
Conversation
This was referenced Jun 23, 2026
Contributor
Author
2 tasks
The backend changed the /v2/config format: the manifest is now an opaque string the SDK stores and replays verbatim, and active_topics + prefetch_blobs moved to the response top level. RemoteConfiguration drops the nested Manifest type accordingly. No production caller yet, so no migration needed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rickvdl
approved these changes
Jun 23, 2026
7c34516 to
448f2ba
Compare
This was referenced Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
After discussions, we changed the manifest from having a parseable body to an opaque string the SDK will just store and pass back to the backend to get the latest version of the config needed.
Note
Medium Risk
This is a breaking wire-format change for remote config sync; callers that still read
manifest.topicsor nested manifest fields must migrate to the new fields.Overview
Remote config
/v2/configparsing now treatsmanifestas an opaque string (store and replay on the next request) instead of a nestedManifestobject with topic etags,prefetch_blobs,prefetched_blobs, andlast_refresh_at.Topic inventory and prefetch hints move to top-level fields:
active_topics(full list of active topic names, including unchanged) andprefetch_blobs. Docs clarify thattopicsstill carries only changed topic bodies.The nested
RemoteConfiguration.Manifesttype is removed.RemoteConfigurationTestis updated for the new JSON shape and assertsmanifestis wrong-type when sent as an object.Reviewed by Cursor Bugbot for commit 448f2ba. Bugbot is set up for automated code reviews on this repo. Configure here.