Weird situation where transition never executes the function and isPending stays true.

[SonnyJimm]

Summary

Hi everyone i have question why this is happening i know i have multiple options that i can choose but i cant understand why is this happening.

When transition + window.history.replaceState + child component calls a server action transitions isPending state never becomes true and transition never calls the function that it wraps also for some reason the order matters if i call replaceState first transition works as expected but if i call the transition before the replaceState this issue happens. i wonder if its a bug or intended behavior.

Additional information

version next: 14.2.35
expected 

 GET /?counter=2 200 in 442ms
Child Action executed 0
 POST /?counter=1 200 in 14ms
Client Action executed 0
 POST /?counter=1 200 in 1009ms
Child Action executed 0
 POST /?counter=1 200 in 9ms
Client Action executed 0
// continues normally

current behavior

 GET /?counter=2 200 in 353ms
Child Action executed 0
 POST /?counter=1 200 in 11ms
Client Action executed 0
 POST /?counter=1 200 in 1008ms
Child Action executed 0
 POST /?counter=1 200 in 10ms
Client Action executed 0
 POST /?counter=1 200 in 1016ms
Child Action executed 1
 POST /?counter=2 200 in 14ms
// transition isPending never becomes false and no client action triggered

### Example

https://github.com/SonnyJimm/next-use-transition-never-resolves

[icyJoseph]

I think you may have forgotten to push the code to the repository? https://github.com/SonnyJimm/next-use-transition-never-resolves is at the start state.