chore: bump NosCore.Packets to 21.0.0 - #495
Conversation
Major rather than patch: GidxFamilySubPacket is gone and GidxPacket's FamilyIdentifier became a nullable FamilyId, so the public surface changed even though nothing in NosCore referenced either. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 30 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Release bump so #494 can reach nuget.org. Nothing has shipped since
20.0.3, so #493 and #494 go out together — meaning the reverted serializer patch never reaches a consumer at all.Major rather than patch because the public surface changed:
GidxFamilySubPacketdeletedGidxPacket.FamilyIdentifier(sub-packet) →GidxPacket.FamilyId(long?)Nothing in NosCore referenced either, so the practical impact is nil, but removing a public type is a major by semver.
115/115 tests pass.
🤖 Generated with Claude Code