Skip to content
Post-merge workflow

fix: When a new key was created, the domain was not set: fixed! #58

Sign in to view logs

fix: When a new key was created, the domain was not set: fixed!

fix: When a new key was created, the domain was not set: fixed! #58

Triggered via pull request June 13, 2024 15:08
@antoniotarriconeantoniotarricone
closed #106
fix_key_creation
Status Failure
Total duration 24m 0s
Artifacts –

post-merge.yml

on: pull_request
post_merge
10m 40s
post_merge
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@antoniotarricone
antoniotarricone
deleted by antoniotarricone Jun 13, 2024
dev-cd

Annotations

1 error and 1 warning
post_merge
Process completed with exit code 1.
post_merge
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab, cycjimmy/semantic-release-action@8e58d20d0f6c8773181f43eb74d6a05e3099571d, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8, actions/setup-java@5ffc13f4174014e2d4d4572b3d74c3fa61aeb2c2, azure/login@92a5484dfaf04ca78a94597f4f19fea633851fa2, azure/CLI@fa0f960f00db49b95fdb54328a767aee31e80105, actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.