Skip to content

release-step-3

release-step-3 #30

Manually triggered April 10, 2026 06:53
Status Success
Total duration 30m 8s
Artifacts –

release-step-3.yml

on: workflow_dispatch
validate-tag
28s
validate-tag
Wait for artifacts to be available on maven central
4s
Wait for artifacts to be available on maven central
Deploy to Maven Central (Buildkite)
0s
Deploy to Maven Central (Buildkite)
Publish AWS Lambda
27m 54s
Publish AWS Lambda
Create GitHub Release
6s
Create GitHub Release
Bump versions and create PR  /  validate-tag
5s
Bump versions and create PR / validate-tag
Build and push docker images
1m 10s
Build and push docker images
Bump versions and create PR  /  Bump versions and create PR
44s
Bump versions and create PR / Bump versions and create PR
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Wait for artifacts to be available on maven central
Unexpected input(s) 'maven-central', 'sonatype-central', valid inputs are ['artifact-id', 'group-id', 'version']
Publish AWS Lambda
No files were found with the provided path: .ci/.arn-file.md. No artifacts will be uploaded.
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://docs.slack.dev/legacy/legacy-messaging/legacy-secondary-message-attachments for more details).
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.