chore: bump packages to 3.0.0 - #52
Merged
Merged
Conversation
Major per the rule-API break in #49; Annotations carries the new [AnchoredDateTime]; the schema tool picks up .slnx support and the fixed generator. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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
Bumps
ModernUO.Serialization.Generator,ModernUO.Serialization.Annotations, andModernUOSchemaGeneratorto 3.0.0 — major per the rule-API break in #49. Annotations carries the new[AnchoredDateTime]; the schema tool picks up.slnxsupport and the rebuilt generator.Pre-publish validation (local packages against the consuming engine)
Packed locally and pointed the full 1,900-class engine solution at the local feed:
3.0.0.0, and the asyncAfterDeserializationclasses carry the qualifiedServer.Timer.DelayCall.One publishing note discovered the hard way: a local
dotnet pack -c Releasereused stale build output and produced a 3.0.0 nupkg containing the 2.14.2 assembly — caught only because the validation checked the assembly version inside the package. The CI publish path (dotnet build -c Releaseon a clean checkout) is not affected, but local packing should always be preceded by a clean.🤖 Generated with Claude Code