feat!: remove compatibility for Biome v1#102
Conversation
BREAKING-CHANGE: Using the extension with Biome v1 is no longer supported. Please upgrade to Biome v2, or use older version of the extension.
|
I'll merge and make a release once Biome v2.0 is released, to reduce confusion for Biome v1 users |
ematipico
left a comment
There was a problem hiding this comment.
@siketyan would you mind updating:
- the version of the
extension.tomlto0.2.0 - update the
README.md. We want to highlight thatv0.1.5of the extension is only compatible with v1.9.4 of Biome, andv0.2.0of the extension is only compatible withv2of biome
|
@ematipico Updated. Feel free to reword the note in README if it's not appropriate. 🙏 |
|
@siketyan Can we have pre-release? All of my projects use Biome v2, so lack of working biome support in Zed is discouraging me from using Zed althogether. |
|
@nakamorichi I am not very familiar with Zed, and not sure if we can publish a pre-release. Do you have a documentation or something? I am happy to do that if possible :) |
|
@siketyan tbh, I'm also very new to Zed. I just noticed there's functionality for "Install another version" in the "Extensions" page, so I assumed it would work similarly to vscode's "Install Specific Version". In vscode I'm using pre-release of biome, because the release version doesn't work for Biome v2, and was hoping similar would be possible in Zed & Biome-Zed. I assume the flow is same as with any extension release - of which you probably know more than me :). I don't know the supported version format syntax, but as long as there's a version containing pre-release changes, it should be possible to select that version manually. I added some screenshots that probably explain better what I mean. It could also be that support for pre-release versions needs to be properly implemented into Zed itself; not sure. https://zed.dev/docs/extensions/developing-extensions?highlight=extens#publishing-your-extension |
|
Are we having this merged now that we have v2 stable released? |
|
@XiNiHa Thanks for the reminder! |
|
FYI, I also just submitted a PR to the Zed Extensions repo, so anyone can get the latest release once it's merged. |
|
Oh, I even didn't know that we require a manual PR 😅 Thank you! |
|
So if I understand correctly, I just realized that v0.2.0 is technically still working with Biome v1 (mostly, but no guarantee in the future), as long as we don't use the |
Warning
Breaking Change: Using the extension with Biome v1 is no longer supported. Please upgrade to Biome v2, or use older version of the extension.
Closes #97
We tried to keep compatibility for Biome v1 in #77, but it seems not working in some environments. Due to lack of debugging tools in Zed, we decided to just drop the support for Biome v1 and release a new major version.
In this pull request, appending
--config-pathin the LSP command line is no longer supported. If you are using a custom configuration path, it no longer work with Biome v1.