Refactor: Add Repository Methods and Remove Direct Access to SubscriptionIndexRepository.repo #746
aji70ci.yml
on: pull_request
Backend DB Migrations (Postgres)
34s
Contract (Rust)
10s
Matrix: backend
Matrix: frontend
Postgres Backup / Restore Drill
0s
Annotations
24 errors and 18 warnings
|
Frontend (Node.js 22)
Process completed with exit code 1.
|
|
Frontend (Node.js 20)
Process completed with exit code 1.
|
|
Contract (Rust)
Process completed with exit code 1.
|
|
Backend DB Migrations (Postgres)
Process completed with exit code 1.
|
|
Backend (Node.js 20):
backend/src/main.ts#L54
Unsafe member access .setTitle on an `any` value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe construction of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 20):
backend/src/main.ts#L53
Unsafe assignment of an `any` value
|
|
Backend (Node.js 20):
backend/src/main.ts#L52
A `require()` style import is forbidden
|
|
Backend (Node.js 20):
backend/src/main.ts#L52
Unsafe assignment of an `any` value
|
|
Backend (Node.js 22):
backend/src/main.ts#L54
Unsafe member access .setTitle on an `any` value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe construction of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe call of an `any` typed value
|
|
Backend (Node.js 22):
backend/src/main.ts#L53
Unsafe assignment of an `any` value
|
|
Backend (Node.js 22):
backend/src/main.ts#L52
A `require()` style import is forbidden
|
|
Backend (Node.js 22):
backend/src/main.ts#L52
Unsafe assignment of an `any` value
|
|
Frontend (Node.js 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Frontend (Node.js 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Contract (Rust)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Backend DB Migrations (Postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Backend (Node.js 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L188
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L182
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L176
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L171
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L165
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 20):
backend/test/feature-flags.e2e-spec.ts#L159
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L188
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L182
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L176
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L171
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L165
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|
|
Backend (Node.js 22):
backend/test/feature-flags.e2e-spec.ts#L159
Unsafe argument of type `any` assigned to a parameter of type `ExecutionContext`
|