Update versioning policy for editor integration#12375
Merged
dhruvmanila merged 2 commits intomainfrom Jul 18, 2024
Merged
Conversation
T-256
reviewed
Jul 18, 2024
Member
Author
|
I initially thought that adding a new capability shouldn't require a minor bump but maybe that's not true. What if we add completions and then when a user upgrades the Ruff version, the editor will start showing completions from Ruff, a lot of which might be duplicates from an existing language server. Edit: I think for now this is fine. |
311dda0 to
4e72992
Compare
MichaReiser
approved these changes
Jul 18, 2024
4e72992 to
dba2cd3
Compare
zanieb
reviewed
Jul 18, 2024
zanieb
reviewed
Jul 18, 2024
zanieb
approved these changes
Jul 18, 2024
Co-authored-by: Zanie Blue <contact@zanie.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Following the stabilization of the Ruff language server, we need to update our versioning policy to account for any changes in it. This could be server settings, capability, etc.
This PR also adds a new section for the VS Code extension which is adopted from Biome's versioning policy for the same.