Closed
Conversation
Member
|
I believe the changes were intentional because some of the features are related to Fable.CLI only. Plus, it can happens that Fable.CLI gets a release when Fable.Compiler doesn't. This is why there is a 1 version offset between both the projects... We should keep it as it is I think, and with the automation of release we will not need to worry about manually updating the changelogs anymore. I am looking into it. |
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
2 participants
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.
@MangelMaxime I assume the changelogs divergence was intentional, so feel free to just close this PR.
But if we manage to keep the versions the same and always release all components at the same time, we might be able to have just one changelog for everything. What do you think?