Skip to content

feat: make settings accessible to widget components #169

feat: make settings accessible to widget components

feat: make settings accessible to widget components #169

Triggered via pull request February 20, 2025 20:49
Status Failure
Total duration 10s
Artifacts

ci.yaml

on: pull_request
Matrix: ci-build
Matrix: ci-repo-check
Matrix: ci-test
Fit to window
Zoom out
Zoom in

Annotations

9 errors
ci-build (macos-latest)
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.
ci-build (windows-latest)
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.
ci-repo-check (macos-latest)
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.
ci-repo-check (ubuntu-latest)
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.
ci-test (ubuntu-latest)
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.
ci-test (macos-latest)
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.
ci-build (ubuntu-latest)
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.
ci-repo-check (windows-latest)
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.
ci-test (windows-latest)
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.