Tags: mattermost/mattermost-plugin-playbooks
Tags
restore the missing Plugin telemetry key (#1866) For now, we're just hard-coding this while still honouring the server configuration as to whether or not to emit telemetry in the first place. In the future, we should integrate knowledge of the service environment and use that to key off which key (if any) to use.
Warn instead of Error on unrecognized user tz (#1859) * Warn instead of Error on unrecognized user tz Instead of erroring out on `/playbook todo` or the weekly digest message, just log a warning when a user's timezone isn't recognized: ``` {"timestamp":"2023-07-21 14:03:56.435 -03:00","level":"warn","msg":"failed to get user timezone","caller":"app/plugin_api.go:979","plugin_id":"playbooks","error":"unknown time zone Asia/Jerusalem2","user_id":"soa5qdiwnig8dkmekej37p8gmw","plugin_caller":"github.com/mattermost/mattermost-plugin-playbooks/server/app/playbook_run_service.go:2262"} ``` In practice, this won't occur because the timezone is really invalid, but because the operating system lacks the necessary tzdata. * e2e tests on mattermost-cloud:latest
[fix] CD revisiting naming for artifacts generated (#1856) We are currently using the scheme: ${GITHUB_REPOSITORY#*/}-${GITHUB_REF_NAME}.tar.gz to name the artifact. CircleCI pipelines used the following naming scheme: ${GITHUB_REF_NAME}.tar.gz. Previous CircleCI release example: https://github.com/mattermost/mattermost-plugin-playbooks/releases/tag/v1.36.2 We are alligning with the previous naming scheme. Signed-off-by: Akis Maziotis <[email protected]>
PreviousNext