Running publisher pipeline specifying an older commit SHA doesn't pick the files from that commit but latest content in those files

[klakshmikantha]

Release version

5.0.1

Describe the bug

When running publisher pipeline with commit id, I am trying to specify an older (not latest but one prior to latest) commit id to deploy those changes but it picks the latest content from those files (latest commit).
We would like to explore this to give an option to re-deploy an older commit changes in case it fails during initial execution and newer changes are made.

Expected behavior

The changes pertaining to the commit SHA specified in the publisher run should be picked and deployed and not the latest commit changes.

Actual behavior

Latest commit changes are taken even if an older commit id is specified.

Reproduction Steps

Pick a older (not latest) commit id and specify in publisher workflow and it picks the values from latest version of the files not the one present in the inputted commit id.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

@klakshmikantha - thanks for raising this. It is a known bug and will be fixed in our next major release.

[klakshmikantha]

Thank you for the confirmation @guythetechie .

[waelkdouh]

@klakshmikantha we just tested under v6.0.0-rc1 and the issue has been resolved. Please test and let us know.