Releases: melexis/warnings-plugin
Releases · melexis/warnings-plugin
Modernize build system and package structure
What's Changed
- Move modules from namespace 'mlx' to 'mlx/warnings' by @JasperCraeghs in #130
Full Changelog: 4.4.0...5.0.0
Enhance Code Quality feature
What's Changed
- Improve documentation for Code Quality feature by @JasperCraeghs in #126
- Add configurability to descriptions of Code Quality report entries by @JasperCraeghs in #129
Full Changelog: 4.3.2...4.4.0
Fix deployment in CI
Fix deployment in CI
New option to generate Code Quality report for GitLab CI
What's Changed
- Tweak regular expressions by @JasperCraeghs in #122
- Update actions due to deprecation warning by @JasperCraeghs in #123
- Generate Code Quality report for GitLab CI by @JasperCraeghs in #121
Full Changelog: 4.2.0...4.3.0
Support RF 5 and YAML for configuration file
Drop support for Python 3.6 and count Sphinx Critical warnings
With Sphinx 5 you also receive CRITICAL
instead of WARNING
, so we should count them in as well.
Even though we dropped Python 3.6 support we still maintain backwards compatibility.
New option to write all counted warnings to a file
- Added option to write all counted warnings/failures to a file [PR #111]
- Dropped official support for Python 3.5
- Started testing Python 3.9 and 3.10
Support exclude feature for Robot and JUnit checkers
- Added support for exclude feature to Robot and JUnit checkers so that all checkers can now benefit from it.
- Fix: set the maximum version of junitparser to avoid compatibility issues.
Bugfix for the lxml
In 3.1.0 when lxml is installed, the use of the JUnitChecker resulted in an error. This release fixes the issue. Details can be found in #105