Repository navigation
Switch releases to two-digit calendar versions - #28
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
Switch stable release versions from
YYYY.MMDD.NtoYY.MMDD.N(for example,26.1112.2) to drop the century digits. The release allocator recognizes existing four-digit tags alongside new two-digit tags, preserving date and same-day counter continuity across the transition.The supported release-date range is 2000-2099 to keep two-digit years unambiguous. New NuGet versions will sort below already-published four-digit-year versions; this ordering change is intentional.
Validation
dotnet run --file scripts/calendar-version.cs -- --test26.1101.7andlatest.