You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have downloaded the latest version and a new one is released, we currently do not fetch the new version but rather use the already downloaded one as latest.
We need to find a way to be able either periodically check in an specific interval since latest was last touched or before every run if there is a new release.
That means we need to store which version is latest.
There are multiple ways, possible via symlinks or to remove the latest terminology.
Would it be appropriate to add an argument that allows a specific version of editorconfig-checker to be used? MegaLinter has a similar wrapper package called mega-linter-runner that accepts a --release argument, for example, and I have found that helpful for pinning MegaLinter.
If we have downloaded the latest version and a new one is released, we currently do not fetch the new version but rather use the already downloaded one as latest.
We need to find a way to be able either periodically check in an specific interval since latest was last touched or before every run if there is a new release.
That means we need to store which version is latest.
There are multiple ways, possible via symlinks or to remove the latest terminology.
Do you have any thoughts on this @septs ?
The text was updated successfully, but these errors were encountered: