Roll the changelog for v0.14.0 — first public release - #33
Merged
Conversation
Everything since the internal 0.1.0 milestone ships as 0.14.0, paired with engine 0.14.3. The header now documents the real version scheme: Desktop shares major.minor with the engine generation; patch numbers advance independently.
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
1 participant
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
Prepares the first public release of MandoCode Desktop. Rolls everything accumulated in [Unreleased] since the internal 0.1.0 milestone into a dated [0.14.0] section with a debut summary, and corrects the changelog header to document the actual version scheme: Desktop shares its major.minor with the engine generation it ships (engine drives 0.14 -> 0.15), while each product's patch number advances independently.
Scope and risk
Documentation only. The csproj already reads 0.14.0, so no code change is needed. Merging this is the last content change before tagging v0.14.0, which triggers the release pipeline for the first time.