Fixed: allowedTags no longer swallows a valid tag that ends up in the same raw match as a stray < (e.g. Values: <10, <20, and <bold>x</bold>). Only the leading < of a disallowed match is neutralized and scanning resumes right after it, matching the escaping semantics react-i18next used before.
Found by react-i18next's test suite while migrating it to the new allowedTags option. See CHANGELOG.md.