{"push_id":654861728,"size":4,"distinct_size":4,"ref":"refs/heads/CAM-3825","head":"987fddfa5ab571533d1bb0e85c56e51588a80a47","before":"51923c9335f66b15b75af1ebb5cd3234dbdf4a1e","commits":[{"sha":"b85b4e6b803b3c106fe79d4cf25aed75ebc2006d","author":{"email":"ae2d9b6e0ae4bf24b0588148b219cdd80d1dcfe4@camunda.com","name":"Thorben Lindhauer"},"message":"fix(engine): error propagation for migrated process instances\n\n- makes use of the activity execution mapping to find an error handling\n  execution when an error is propagated\n- ensures compatibility with process instances started pre 7.3\n\nrelated to CAM-3825","distinct":true,"url":"https://api.github.com/repos/camunda/camunda-bpm-platform/commits/b85b4e6b803b3c106fe79d4cf25aed75ebc2006d"},{"sha":"ef47682143350a131e3a36113f5d187a33cce016","author":{"email":"ae2d9b6e0ae4bf24b0588148b219cdd80d1dcfe4@camunda.com","name":"Thorben Lindhauer"},"message":"fix(engine): fix activity execution mapping during state transition\n\n- operation activity end: when a scope execution has already been destroyed\n  and removed, the scope activity is set on its concurrent parent. in this\n  case, the scope activity should not be considered for the mapping\n\nrelated to CAM-3825","distinct":true,"url":"https://api.github.com/repos/camunda/camunda-bpm-platform/commits/ef47682143350a131e3a36113f5d187a33cce016"},{"sha":"fc97e9fd49472bdb78ec120e4bbb6cdc3fce588d","author":{"email":"ae2d9b6e0ae4bf24b0588148b219cdd80d1dcfe4@camunda.com","name":"Thorben Lindhauer"},"message":"fix(engine): legacy event subprocess synchronization\n\nrelated to CAM-3825","distinct":true,"url":"https://api.github.com/repos/camunda/camunda-bpm-platform/commits/fc97e9fd49472bdb78ec120e4bbb6cdc3fce588d"},{"sha":"987fddfa5ab571533d1bb0e85c56e51588a80a47","author":{"email":"ae2d9b6e0ae4bf24b0588148b219cdd80d1dcfe4@camunda.com","name":"Thorben Lindhauer"},"message":"fix(engine/migration): activity instance tree for multi-instance\n\n- for pre 7.3 instances, the assumption that a scope execution's parent\n  always contains the activity instance id for the scope execution's scope\n  does not always hold\n- in case of multi-instance, the assignment is not correct. this commit\n  ensures that the activity instance tree is somewhat useable in such\n  a case\n\nrelated to CAM-3825","distinct":true,"url":"https://api.github.com/repos/camunda/camunda-bpm-platform/commits/987fddfa5ab571533d1bb0e85c56e51588a80a47"}]}