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.
This is just a copy of a changelog from the extension repo, meaning it doesn't represent changes actually made to the server side. So it is just a maintance burden to keep it in sync with the extension's changelog with no clear benifits. Morover, currently even though the server is separated from the extension, they are still very much tied together and server changes are motivated only by extension's needs. My idea is to change that when the server becomes a separate thing (#33) and version it separately as well (e.g. starting from
1.0.0
), but I don't think we've reached the quality bar for this yet. If that plan comes true though we will have to rewrite the changelog with the respect to new versioning anyway, so it is +1 reason to remove current changelog and not bother copying it every time we release a new extension version