-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
🐛 --staged regression in v1.8.0 #3069
🐛 --staged regression in v1.8.0 #3069
Comments
Thank you for reporting it! @unvalley are you able to take a look? |
Amazing to see it fixed already! Do you know already when you‘ll publish this fix? Just so I know whether we should revert to v1.7.3 or we can wait for the fix to land. :) |
We usually release a patch in a weekly window. You can expect the patch to be released by next Tuesday. |
Everything is good, I was on 1.8.0 and noticed the same regression. Updating to 1.8.3, things are nice and stable now. |
Environment information
What happened?
As of v1.8.0, the
--staged
flag doesn’t seem to work properly anymore. In v1.7.3, it would only run on staged files. But in v1.8.0, we get reports in files that are not staged (not even touched, for that matter).I suspect the error to be related to this merge-request, since it updated which files would end up being considered. I may be wrong.
Expected result
Only the files that are staged by git (or whatever VCS is supported) should be linted when running Biome with the --staged flag.
Code of Conduct
The text was updated successfully, but these errors were encountered: