This issue also affected the 1.0.1 CoC that was the current CoC for many years. Few people noticed since the version was the same year. The CoC is "backdated" so that all the signers of 1.0 and 1.0.1 are automatic signers of 1.1.
The correct fix is to add a separate attribute or rule to the model that manages compatibility. If all minor versions are backward compatible with their major version (ie 1.x is incompatible with 2.x) then the model could have a parsing rule instead of a date matching rule.
This issue also affected the 1.0.1 CoC that was the current CoC for many years. Few people noticed since the version was the same year. The CoC is "backdated" so that all the signers of 1.0 and 1.0.1 are automatic signers of 1.1.
The correct fix is to add a separate attribute or rule to the model that manages compatibility. If all minor versions are backward compatible with their major version (ie 1.x is incompatible with 2.x) then the model could have a parsing rule instead of a date matching rule.