[Bug]: Create Crate Version Update PR leaves PR in a state with no CI tests

Is there an existing issue for this?

• I have searched existing issues

Current Behavior

The initial manual creation of the PR for updating the crate version via the crate-version-update workflow works as expected. However, if another PR is merged and the automatic run of the workflow triggers to update the PR, the PR is left in a state of being updated, but not having CI trigger for it.

Expected Behavior

CI should trigger whenever the Crate Update PR is updated (commits only)

Steps To Reproduce

1. Manually run the crate-version-update workflow
2. Merge a different PR
3. Watch as the crate-version-update PR successfully runs and updates the PR, but CI does not re-trigger

Build Environment

N/A

Version Information

N/A

Urgency

Medium

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

My initial thoughts is that it has to do with force pushing a commit that is exactly the same as the commit that already exists. I think github sees the new push and thus wipes the status checks, but then also sees the commit added is exactly the same and thus does not re-run CI.

I'm not sure this 100% makes sense as this is basically the same as a rebase&FF. Not sure. Needs further investigation.