Releases: qa-guru/allure-notifications
Releases · qa-guru/allure-notifications
4.8.0
Added
- #284 Add ability to publish suites statistics (check the configuration option
enableSuitesPublishing
) - #304 Add ability to publish custom data specified in the configuration (check
customData
block in the configuration) - #305, #306 Add ability to specify CC and BCC recipients in e-mails
- #310 Ignore whitespaces while parsing e-mail recipients from configuration
Changed
- #292 (Fixes #273) Use new file upload API to publish Slack notifications
More details: https://api.slack.com/changelog/2024-04-a-better-way-to-upload-files-is-here-to-stay
Deprecated
- #305 Deprecate
recipient
e-mail configuration option in favour of newto
e-mail configuration option
Fixed
- Fix Log4J config location
- #307 Replace unsafe System exit method with exception in case of invalid email address provided
Full Changelog: 4.7.0...4.8.0
4.7.0
4.6.1
4.6.0
4.5.0
4.4.0
4.3.0
4.2.1
- enabled publishing of multiple notifications at once
- enabled support of
STARTTLS
protocol for emails:- securityProtocol (optional: can be omitted or set to
null
) - one of the following security protocols: - SSL - use SSL to connect (make sure the SSL port is used).
- STARTTLS - use of the STARTTLS command (if supported by the server) to switch the connection to
- securityProtocol (optional: can be omitted or set to
4.2.0
- Added support for the Belarusian (by) language
- Added the ability to add a message icon (parameter “logo” in config file)
- Refactoring. Improving the Design of Existing Code
4.1 Release
version 4.1 version 4.1