Skip to content
Deploy to staging

fix: rm attempt to log error on successful GETs #104

Sign in to view logs

fix: rm attempt to log error on successful GETs

fix: rm attempt to log error on successful GETs #104

Triggered via pull request June 13, 2024 07:54
@NilsOveTenNilsOveTen
opened #30
fix/not/rm-attempt-to-log-error-on-successful-get
Status Success
Total duration 2m 3s
Artifacts –

deploy-staging.yaml

on: pull_request
Run tests
1m 32s
Run tests
Build query-cache when pull request is created  /  Build, test, publish staging
56s
Build query-cache when pull request is created / Build, test, publish staging
Deploy to staging environment with reusable workflow  /  Deploy to staging environment
13s
Deploy to staging environment with reusable workflow / Deploy to staging environment
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Run tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-go@v2, codecov/codecov-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/