Fixed
- Fix a race condition for recalculating a diff following a rebase. After a branch is rebased, an asynchronous job is queued to recalculate the diff for that branch. If a user tried to update the diff for that branch or merge the branch before the recalculation completed then they would receive an error like
ResourceNotFoundError: Multiple diffs for branch ... with tracking_id .... The diff update logic is now updated to handle post-rebase recalculation correctly if it is reached before the recalculation job. (#9898) - Removing a node from the schema on a branch and merging that branch no longer fails with a
SchemaNotFoundError. Schema elements without a persisted id (such as the virtualprofilesrelationship) are now compared by value instead of being reported as spurious additions in the schema diff. (#9899) - Fresh installations now persist the deprecated-model markers, so the core-schema diff computed by
infrahub upgradestarts out empty instead of always reportingLineageSourceandLineageOwneras changed on an up-to-date installation. - Merging a rebased branch now computes schema migrations against the rebase point, so schema changes the rebase already incorporated from the destination branch are no longer counted a second time.
- Schema errors raised during background operations (such as
SchemaNotFoundError) now surface the actual error instead of an unrelated serializationTypeError.
Full Changelog: infrahub-v1.10.4...infrahub-v1.10.5