Looks like this happens because we bump gemspec and do actually release in different jobs and the second job didn't get the latest code, instead it gets repo for sha where it was triggered
Expected result
We need to make sure that gem is released with exact version which in the repo
Problem
During patch release 1.2.2 was observed that 1.2.1 was released, but 1.2.2 was committed https://github.com/lutaml/expressir/actions/runs/1978865314
Looks like this happens because we bump gemspec and do actually release in different jobs and the second job didn't get the latest code, instead it gets repo for sha where it was triggered
Expected result
We need to make sure that gem is released with exact version which in the repo
Upd: exact the same issue https://github.com/actions/checkout/issues/439