Connection Migration: Connection ID does not change after path switch (wired/wireless client)

I am testing connection migration in quic-go with a client that is connected via both wired and wireless interfaces. During path validation, a different Connection ID is used for each path as expected. However, after switching the active path (e.g., from wired to wireless), the Connection ID used for communication remains the same as before the migration.

Is this the intended behavior according to the QUIC specification and quic-go's design? Or should a new Connection ID always be used after a successful path migration, in order to prevent linkability and tracking as described in the QUIC RFC? If this is not expected, could you clarify under what conditions the Connection ID should be switched in quic-go?