Releases: neonidian/teams-notify-build-status
Releases · neonidian/teams-notify-build-status
Auto publish major version
What's Changed
- #37 Add workflow for publishing major version by @neonidian in #38
Full Changelog: v3.0.4...v3.0.5
Upgrade dependencies
Upgrade npm and actions dependencies
Change failure message on HTTP request failure
Update logging message
- Failure and logging message have been updated
Full Changelog: v3.0.1...v3.0.2
Update error message for incorrect title Background color
What's Changed
- Update error message for incorrect title background color
- action.yml - Fix typo
Full Changelog: v3.0.0...v3.0.1
Option to set title background color
What's Changed
- Enhancement: Set title background color by @neonidian in #27
- Move to semantic versioning with this major version release
Full Changelog: v2.3...v3.0.0
Change HTTP client
What's Changed
Change HTTP client from axios to GitHub provided @actions/http-client in #25
Significantly reduces the artifact size from ~174 kb to ~ 67 kb
GitHub says this is optimized to be used for GitHub actions
Full Changelog: v2.2.1...v2.3
Add style property to title
What's Changed
- Add style property to title in #23 to mark the text block as a heading for accessiblity
Full Changelog: v2.2...v2.2.1
Add optional title
What's Changed
- Add optional title input to messagecard. Displays a larger text at the top of the card
Full Changelog: v2.1...v2.2
Remove core.notice logging, set failure if response != 1
What's Changed
- Remove core.notice which shows a notice in the actions page like 'Message has been sent to Teams'. This has been replaced with core.info which logs inside the action
- Set action as failed if the response body does not contain the value 1. This is done because Teams always returns status code 200 and any other status code if any is wrapped inside the response body. status code 200 with response body 1 means the message send is successful
Full Changelog: v2.0.2...v2.1