Skip to content

Fix M2M authentication and add clock tolerance to JWT methods #204

Fix M2M authentication and add clock tolerance to JWT methods

Fix M2M authentication and add clock tolerance to JWT methods #204

Triggered via pull request July 24, 2024 13:58
Status Failure
Total duration 36s
Artifacts

ruby.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
test (3.0)
Process completed with exit code 1.
test (3.1)
Process completed with exit code 1.
test (2.7)
Process completed with exit code 1.
test (3.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.1)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (2.7)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/