Pytest 4.5.0 now displays warning for non declared markers (Eventually errors)

When using allure, we are now seeing the following outputs with pytest 4.5.0 (These warnings are eventually going to become errors in pytest 4.6.0 (or some time similar)

some (but not all examples are):

PytestUnknownMarkWarning,_pytest/mark/structures.py:324: PytestUnknownMarkWarning: Unknown pytest.mark.allure_label.epic - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html PytestUnknownMarkWarning,

pytest.mark.allure_label.feature - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html PytestUnknownMarkWarning,

pytest.mark.allure_label.story - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.htmlPytestUnknownMarkWarning,

#5023: New flag --strict-markers that triggers an error when unknown markers (e.g. those not registered using the markers option in the configuration file) are used in the test suite.

The existing --strict option has the same behavior currently, but can be augmented in the future for additional checks.

https://docs.pytest.org/en/latest/changelog.html

[sseliverstov]

will be fixed on next release

[jurisbu]

This is very annoying.