fixed mcp server disposition issues #152
gallaylAnnotations
15 errors and 2 warnings
|
Lint, Build and test (24.x)
Process completed with exit code 2.
|
|
Lint, Build and test (24.x):
frontend/src/pages/stacks/stack-setup.tsx#L71
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
|
|
Lint, Build and test (24.x):
frontend/src/pages/settings/api-tokens-section.tsx#L53
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<PublicApiToken>'.
|
|
Lint, Build and test (24.x):
frontend/src/pages/services/services-list.tsx#L40
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
|
|
Lint, Build and test (24.x):
frontend/src/pages/services/service-detail/history-tab.tsx#L77
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceStateHistory>'.
|
|
Lint, Build and test (24.x):
frontend/src/components/repository-table.tsx#L37
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<GitHubRepository>'.
|
|
Lint, Build and test (24.x):
frontend/src/components/prerequisite-table.tsx#L43
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<Prerequisite>'.
|
|
Lint, Build and test (22.x)
The strategy configuration was canceled because "build._24_x" failed
|
|
Lint, Build and test (22.x)
The operation was canceled.
|
|
Lint, Build and test (22.x):
frontend/src/pages/stacks/stack-setup.tsx#L71
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
|
|
Lint, Build and test (22.x):
frontend/src/pages/settings/api-tokens-section.tsx#L53
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<PublicApiToken>'.
|
|
Lint, Build and test (22.x):
frontend/src/pages/services/services-list.tsx#L40
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceView>'.
|
|
Lint, Build and test (22.x):
frontend/src/pages/services/service-detail/history-tab.tsx#L77
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<ServiceStateHistory>'.
|
|
Lint, Build and test (22.x):
frontend/src/components/repository-table.tsx#L37
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<GitHubRepository>'.
|
|
Lint, Build and test (22.x):
frontend/src/components/prerequisite-table.tsx#L43
Object literal may only specify known properties, and 'idField' does not exist in type 'CollectionServiceOptions<Prerequisite>'.
|
|
Lint, Build and test (24.x)
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/
|
|
Lint, Build and test (22.x)
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/
|