Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalidate latest #385

Open
mstruebing opened this issue Mar 5, 2022 · 1 comment
Open

Invalidate latest #385

mstruebing opened this issue Mar 5, 2022 · 1 comment

Comments

@mstruebing
Copy link
Member

mstruebing commented Mar 5, 2022

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 ?

@Kurt-von-Laven
Copy link

Kurt-von-Laven commented May 12, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants