[Bug]: Publishing Same Version of a Tool to Local Repository Doesn't Pick the Latest Published Version

[ThisaruGuruge]

Description

When a Ballerina CLI tool is developed, the experience should be that the developers should be able to publish the tool to the local repository and pull it back for testing. In this case, the same version of the tool can be published for multiple times to the local repository.

But if the published version (to the local repository) is the same as the one in the distribution (which is the case for Alpha pack testing), the locally pushed pack is not picked, even when the

bal pull grpahql:1.0.0 --repository=local

is executed.

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Update Tool

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[ThisaruGuruge]

Tried this again and it seems to be working. Closing the issue. Will reopen if I observe this issue again.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.