chore(main): release 1.48.0 (#1786) #65
dialogporten-botci-cd-prod.yml
on: push
Get current version
/
Filter
3s
Get Latest Deployed Version Info from GitHub
/
Get Latest Deployed Versions from GitHub Variables
0s
Dry run deploy apps to prod
/
deploy-migration-job
Store Latest Deployed Infra Version as GitHub Variable
/
Store GitHub Environment Variable
Matrix: Dry run deploy apps to prod / deploy-apps
Waiting for pending jobs
Matrix: Dry run deploy apps to prod / deploy-jobs
Waiting for pending jobs
Matrix: Deploy apps to prod / deploy-apps
Waiting for pending jobs
Matrix: Deploy apps to prod / deploy-jobs
Waiting for pending jobs
Store Latest Deployed Apps Version as GitHub Variable
/
Store GitHub Environment Variable
Send Slack message on failure
/
Send Slack message
4s
Annotations
1 error and 2 warnings
|
Get Latest Deployed Version Info from GitHub / Get Latest Deployed Versions from GitHub Variables
The deployment was rejected or didn't satisfy other protection rules.
|
|
Send Slack message on failure / Send Slack message
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
|
|
Send Slack message on failure / Send Slack message
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
|