Skip to content

206 trackedchange additions retain the catalogs nested component instead of rebinding to the canonical instance - #213

Merged
AadilLatif merged 5 commits into
mainfrom
206-trackedchange-additions-retain-the-catalogs-nested-component-instead-of-rebinding-to-the-canonical-instance
Sep 1, 2026
Merged

AadilLatif merged 5 commits into
mainfrom
206-trackedchange-additions-retain-the-catalogs-nested-component-instead-of-rebinding-to-the-canonical-instance

Conversation

@AadilLatif

Copy link
Copy Markdown
Collaborator

Change Summary

Related issue number

Checklist

  • The pull request title is a good summary of the changes.
  • Tests for the changes exist
  • Tests pass on CI
  • Documentation reflects the changes where applicable
  • My PR is ready to review, please add a comment including "please review" to assign reviewers

@sonarqubecloud

sonarqubecloud Bot commented Sep 1, 2026

Copy link
Copy Markdown

@AadilLatif
AadilLatif merged commit 6c37cfc into main Sep 1, 2026
5 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.

TrackedChange additions retain the catalog's nested component instead of rebinding to the canonical instance

1 participant