fix(core): preserve provider identity in catalog updates - #46948
Merged
Conversation
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
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.
Why
A provider update could change
provider.idwhile leaving the catalog entry indexed under its original ID. Listing the provider then advertised an ID that could not retrieve that entry. Agent, model, skill, and integration updates already preserve their keyed identities.What Changes
Provider updates now restore the ID passed to
updateafter the callback completes. Other field edits still apply.original, assigning IDrenamedand nameUpdatedoriginal, but reports IDrenamedoriginaland reports IDoriginal; name becomesUpdatedrenamedThe regression covers creation, an existing provider, editor reads, public lookup/listing, and replay after reload.
Scope
One runtime assignment in
Catalog.provider.update, matching the existing model-editor behavior. This does not redesign editor methods or make all returned catalog values immutable.Verification
The focused regression failed before the fix (
originalexpected,renamedreceived). After the fix, all 59 focused tests pass, including the regression; Core typechecking and formatting pass. The normal pre-push workspace typecheck also passed.