Open jonz94 opened 1 year ago
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.
Prerequisites
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.
Steps to Reproduce
Setup ScoopInstaller/GithubActions' Excavator: https://github.com/matthewjberger/scoop-nerd-fonts/blob/cc6f18bed7936446d79162d72896d7753788e257/.github/workflows/schedule.yml
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
Scoop Config
PowerShell Version
Additional Softwares
No response