Skip to content

release-step-3

release-step-3 #14

Manually triggered March 3, 2025 13:58
Status Failure
Total duration 22s
Artifacts

release-step-3.yml

on: workflow_dispatch
validate-tag
4s
validate-tag
Wait for artifacts to be available on maven central
0s
Wait for artifacts to be available on maven central
Deploy to Maven Central (Buildkite)
0s
Deploy to Maven Central (Buildkite)
Publish AWS Lambda
0s
Publish AWS Lambda
Bump versions and create PR  /  validate-tag
Bump versions and create PR / validate-tag
Bump versions and create PR  /  Bump versions and create PR
Bump versions and create PR / Bump versions and create PR
Update Major Branch
0s
Update Major Branch
Create GitHub Release
0s
Create GitHub Release
Build and push docker images
0s
Build and push docker images
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
validate-tag
Process completed with exit code 1.
notify
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.
notify
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).