Skip to content

fix: use env variable to set jwt secret #214

fix: use env variable to set jwt secret

fix: use env variable to set jwt secret #214

Triggered via push December 25, 2024 14:59
Status Success
Total duration 6m 23s
Artifacts
Run backend tests
4m 22s
Run backend tests
Run backend rubocop
19s
Run backend rubocop
Run backend security
15s
Run backend security
Deploy backend app
1m 48s
Deploy backend app
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Run backend tests
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down
Run backend tests
Unexpected input(s) 'working-directory', valid inputs are ['path', 'key', 'restore-keys', 'upload-chunk-size']
Run backend tests
Unexpected input(s) 'working-directory', valid inputs are ['path', 'key', 'restore-keys', 'upload-chunk-size']
Deploy backend app
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Deploy backend app
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/