-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v1.4.0 #203
Release v1.4.0 #203
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #203 +/- ##
=======================================
Coverage 40.09% 40.09%
=======================================
Files 6 6
Lines 833 833
=======================================
Hits 334 334
Misses 479 479
Partials 20 20 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
@mickmister or @hanzei I'm running through the release test now but, I wonder why there is no CI for For release testing as a precaution, I like to use the binary that came from the pipeline instead of compiling locally. Does CI produce a build here I can use? |
/update-branch |
@DHaussermann The branch needed an update to have the github action workflows. Check the bottom of this page for the built plugin https://github.com/mattermost/mattermost-plugin-autolink/actions/runs/4437991164?pr=203 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and passed
- Reviewed code changes since last release
- Added one test to cover a functional change
- Ran through all tests in Zephyr
- No new issues found
- As a precaution ran the binary from the pipeline on both a Mac OS hosted Mattermost instance as well as our Cloud infrastructure
- Version bump is correct at
1.4.0
LGTM!
Summary
Release for #201
Ticket Link
Part of #202