Change how we're flagging new modules

Old way would catch modules introduced in `1.1` during version `3.1.1`
— this way shouldn’t, while still accounting for `3.1` being new in
`3.1.1` and `3.1-dev` and `3.1-beta1`

Props @beaulebens for the bug report.