[BUG]: Github Action Excavator sometimes downgrade package version

[jonz94]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

Github Action Excavator

Expected/Current Behaviour

Sometimes, the Excavator Action will pick up an older version of a package and assume that older version is the latest version; as a result, it make package downgrade to the older version.

But usually, the next Excavator Action will correctly pick up the latest version, and then make package upgrade back to original version.

• e.g.: matthewjberger/scoop-nerd-fonts@6c26240...cc6f18b
  • corresponding Excavator Action: https://github.com/matthewjberger/scoop-nerd-fonts/actions/runs/3307070805/jobs/5458425517
  • backup logs.zip: github.com-matthewjberger-scoop-nerd-fonts-actions-runs-3307070805-jobs-5458425517-logs.zip

Steps to Reproduce

1. Setup ScoopInstaller/GithubActions' Excavator: https://github.com/matthewjberger/scoop-nerd-fonts/blob/cc6f18bed7936446d79162d72896d7753788e257/.github/workflows/schedule.yml

2. Then the Excavator Action will run every hour, and some of them will have similar behavior as above descriptions.

Possible Solution

I'm not sure what is the root cause of this issue, will add more information if I found any.

Scoop and Buckets Version

Same as https://github.com/ScoopInstaller/GithubActions

Scoop Config

Same as https://github.com/ScoopInstaller/GithubActions

PowerShell Version

Same as https://github.com/ScoopInstaller/GithubActions

Additional Softwares

No response

[rashil2000]

Sometimes, the Excavator Action will pick up an older version of a package and assume that older version is the latest version; as a result, it make package downgrade to the older version.

But usually, the next Excavator Action will correctly pick up the latest version, and then make package upgrade back to original version.

My guess is it's related to some server or network side caching - which on rare occasions makes GitHub Actions runner see an older releases page.