Create a hotfix release from refs/heads/maint/v367 #373
dev_on_dispatch_release_build_hotfix.yml
on: workflow_dispatch
Check worflow ref
4s
Pro staging
/
deploy_on_firebase
1m 45s
Pro integration
/
deploy_on_firebase
1m 16s
Pro production
/
deploy_on_firebase
1m 49s
slack-notification
7s
Annotations
6 warnings
|
Pro staging / deploy_on_firebase
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|
|
Pro staging / deploy_on_firebase
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|
|
Pro production / deploy_on_firebase
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|
|
Pro production / deploy_on_firebase
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|
|
slack-notification
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).
|
|
slack-notification
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.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pass-culture~pass-culture-main~TCSAR1.dockerbuild
|
88 KB |
sha256:0f164dec70ebfc4a63ffb1994934efac99f9fcaf8041890c0da049c97eb3740e
|
|
|
pass-culture~pass-culture-main~UX84WY.dockerbuild
|
39.1 KB |
sha256:51e2ea0e9989e49081de7fb09fc4de3600cdf847a8baa377d3963f72143d02b3
|
|