Lockable resources with inversePrecedence=true is not functioning correctly when used in the steps block of a Declarative Pipeline. The locked resource is locked correctly but when released it does not grant the lock to the newest build but instead the first one that requested it, as if inversePrecedence=false.

I discovered that if you use the lock in the when block of the Declarative Pipeline the inversePrecedence behaves as expected.