cannot find package "github.com/mattermost/mattermost-server/v5/model" about action-mattermost-notify

[nickboldt]

PR that might fix this: #8 (needs approval by the Mattermost Gods).

[nickboldt]

Hmmm. Maybe we should stick with an alpine base image instead of switching to scratch? I hadn't considered that other files in the container are being used (eg., certificates). WDYT @cpanato ?

[cpanato]

released https://github.com/mattermost/action-mattermost-notify/releases/tag/1.1.0

[cpanato]

thanks for the issue, i will check and get this fixed

[nickboldt]

Is this because there's no v5 release/tag/branch, but there is a https://github.com/mattermost/mattermost-server/tree/v5.26.0 and the latest release is https://github.com/mattermost/mattermost-server/releases/tag/v5.37.0 ?

Do you need a floating tag or branch located at https://github.com/mattermost/mattermost-server/tree/v5 that points to the latest code, so that notify 1.0.4 can resolve sources from server v5?

Or should the code in this repo be pinned to a specific server version like v5.2.6.0 or v5.37.0, rather than just v5?

[donjetam]

Is this because there's no v5 release/tag/branch, but there is a https://github.com/mattermost/mattermost-server/tree/v5.26.0 and the latest release is https://github.com/mattermost/mattermost-server/releases/tag/v5.37.0 ?

Do you need a floating tag or branch located at https://github.com/mattermost/mattermost-server/tree/v5 that points to the latest code, so that notify 1.0.4 can resolve sources from server v5?

Or should the code in this repo be pinned to a specific server version like v5.2.6.0 or v5.37.0, rather than just v5?

Second suggestion looks good. Can you please do the changes?

[nickboldt]

To which version would you like the pin? latest stable release 5.37.0? or latest branched release 5.26.0?

[donjetam]

Latest realse v5.37.0 it will be fine.

Having the same issue on our end

[cpanato]

#8 should fix it

[donjetam]

After Im using new tag @1.0.3, I have these error message

Run mattermost/[email protected]
/usr/local/bin/docker run --name e226b722a4416b624493b7808ea54a5d94f3_f8f3e0 --label 60e226 --workdir /github/workspace --rm -e APPLICATION_NAME -e MATTERMOST_WEBHOOK_URL -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" -v "/runner/_work/_temp/_runner_file_commands":"/github/file_commands" -v "/runner/_work/github-action-test/github-action-test":"/github/workspace" 60e226:b722a4416b624493b7808ea54a5d94f3
2021/07/26 13:12:05 error sending message: requesting: Post "***": x509: certificate signed by unknown authority

[cpanato]

thanks for let us know

tested with 1.03 and confirmed that is not working and I've made a change and it is working now
https://github.com/cpanato/testing-ci-providers/runs/3162121062?check_suite_focus=true

will open a PR shortly

[nickboldt]

Will you be able to re-release 1.0.3 with this fix, or will this require a 1.0.4 ?

[cpanato]

will need a new release