Fix broken previous tag within release statements

[No767]

Summary

This PR aims to fix the old behavior of using the newly created tag by pulling the previous tag before the new one has been minted. For example, it used to be v0.1.0...v0.1.0, but now is actually v0.1.0...v0.2.0. This actually has been tested

Types of changes

What types of changes does your code introduce to Rodhaj
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows (except pre-commit.ci) pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud