Add prerelease version support, bump version 1.1.0-beta.1 - #971
Merged
Conversation
albertospelta
changed the title
AppVersion now exposes SemanticVersion, so the About dialog and window title include the prerelease tag, while the copy action uses the informational version with the commit id. Update checks compare all four file-version fields because a prerelease and its final release share Major.Minor.Patch. Artifact names use SemVer 2 for the same reason.
albertospelta
force-pushed
the
alberto/support-prerelease
branch
from
September 3, 2026 14:41
adbf1df to
8934904
Compare
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.
This PR adds support for prerelease versions using Nerdbank.GitVersioning (NBGV).
Application version information is now exposed through the new
AppVersionclass, including semantic, file, and informational versions. The UI, telemetry, diagnostics, update checks, and build artifacts have been updated to use the appropriate version representation.The versioning strategy and the rationale behind these choices are documented in
docs/design/versioning.md.This PR also adds and updates repository documentation for agents, code conventions, and documentation guidelines.