Skip to content

Create a hotfix release from refs/heads/maint/v379 #390

Create a hotfix release from refs/heads/maint/v379

Create a hotfix release from refs/heads/maint/v379 #390

Manually triggered November 24, 2025 14:27
Status Success
Total duration 8m 56s
Artifacts 4
Check worflow ref
2s
Check worflow ref
Find hotfix tag number
39s
Find hotfix tag number
Matrix: Build and tag version / Build Docker images
Matrix: Build and tag version / Push Docker images
Build and tag version  /  tag-and-push-release
19s
Build and tag version / tag-and-push-release
Pro staging  /  deploy_on_firebase
1m 38s
Pro staging / deploy_on_firebase
Pro integration  /  deploy_on_firebase
1m 22s
Pro integration / deploy_on_firebase
Pro production  /  deploy_on_firebase
1m 36s
Pro production / deploy_on_firebase
slack-notification
5s
slack-notification
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
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.
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.
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~03PI4Y.dockerbuild
88.9 KB
sha256:f5aa0aa646e510f8e851fea71b053096ac8b4344e008024f71905c85e1402228
pass-culture~pass-culture-main~MVUXR0.dockerbuild
94.4 KB
sha256:4c3e51f27f35b7c811b1b6af7e0bdc699e25843df488790af3eea458c23cf0c6
pcapi-379.0.1.tar Expired
307 MB
sha256:e7fa692a649c028670ee4ea200ed45fc250e75c5cdb5b059a981b51d576b2669
pcapi-console-379.0.1.tar Expired
522 MB
sha256:bed3bc03d6cceb705738cabb9292eab6c5c90cc4cc546d9c903b63928a4fb961