fix: bugs that the latest tag is not parsed

[sasakisasaki]

Description

Fix a bug that the newest tag is not applied for the created PRs.

Tests performed

The tests are performed by using this repository. The used workflow is provided here. Also you can see the result of the workflow from here.

We verified the following test is passed:

Condition:

• Fix the current version to be 0.0.1
• On the target repository, there are tags like:
  • 7.3.3, 7.3.2, ... , 0.9.0, 0.8.0, ... 0.1.1, 0.1.0, and 0.0.1

What is tested?:

• If we use --targets major minor patch, the following update PRs are created
  • 0.0.1 => 7.3.3 link to the PR
  • 0.0.1 => 0.9.0 link to the PR

Notes for reviewers

Any proposal and comments are highly appreciated! For example, please let us know missing / effective test strategies for this PR. I'm happy for performing the proposed tests and applying code change proposals, ... etc 👍

Interface changes

No change

ROS Topic Changes

No change

ROS Parameter Changes

No change

Effects on system behavior

Due to the bug fix, some possible version update PRs will be created on the autowarefoundation/autoware

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.
• The PR has been properly tested.
• The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.
• The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

[mitsudome-r]

LGTM