Skip to content

fix(security): replace python-jose with PyJWT - eliminates ecdsa vuln… #5

fix(security): replace python-jose with PyJWT - eliminates ecdsa vuln…

fix(security): replace python-jose with PyJWT - eliminates ecdsa vuln… #5

Triggered via push January 18, 2026 14:27
Status Failure
Total duration 11s
Artifacts

test.yml

on: push
Matrix: test
integration
0s
integration
quality
0s
quality
Fit to window
Zoom out
Zoom in

Annotations

13 errors
test (ubuntu-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (ubuntu-latest, 3.12)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (ubuntu-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (ubuntu-latest, 3.13)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (windows-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (windows-latest, 3.12)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (windows-latest, 3.13)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (macos-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (windows-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (macos-latest, 3.12)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (macos-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
test (macos-latest, 3.13)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
status
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings