Repository navigation
release-step-3 #32
SylvainJugerelease-step-3.yml
on: workflow_dispatch
validate-tag
50s
Wait for artifacts to be available on maven central
28m 37s
Bump versions and create PR
/
Bump versions and create PR
48s
notify
4s
Annotations
8 warnings and 1 notice
|
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.
|
|
Create GitHub Release
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
Create GitHub Release
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
Bump versions and create PR / Bump versions and create PR
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
Bump versions and create PR / Bump versions and create PR
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
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.
|
|
Buildkite Build URL
https://buildkite.com/elastic/apm-agent-java-release/builds/49
|