I've noticed that your docs assume that the YY/0Y component of a CalVer date will only be one or two digits.
Specifically, the suggested regex for parsing YY is (?:[1-9][0-9]?) and for 0Y is (?:[0-9]{2}):
(I haven't tried changing my system calendar to see the actual behaviour.)
By contrast, calver.org shows the example of 2106 being rendered as 106 for YY and 0Y:
I'm aware you don't claim to exactly align with that particular website and it's certainly an edge case, but thought it might be worth considering.
I've noticed that your docs assume that the YY/0Y component of a CalVer date will only be one or two digits.
Specifically, the suggested regex for parsing YY is
(?:[1-9][0-9]?)and for 0Y is(?:[0-9]{2}):(I haven't tried changing my system calendar to see the actual behaviour.)
By contrast, calver.org shows the example of 2106 being rendered as 106 for YY and 0Y:
I'm aware you don't claim to exactly align with that particular website and it's certainly an edge case, but thought it might be worth considering.