update GraphQL-ESLint to v4 in Schema Policies #16494
pr.yaml
on: pull_request
Matrix: build / build-and-dockerize
alpha
/
cli-artifacts
4m 56s
alpha
/
...
/
snapshot
2m 17s
graphql-breaking-changes
/
search-token
0s
db-types
/
diff
2m 30s
test
/
db-migrations
1m 21s
test
/
unit
1m 52s
code-style
/
eslint-and-prettier
3m 7s
typescript
/
typecheck
4m 24s
website-preview
/
deployment
3m 33s
storybook-preview
/
deployment
3m 23s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
Matrix: alpha / cli-test
graphql-breaking-changes
/
check
16s
test
/
e2e
3m 45s
Matrix: test / integration
alpha
/
...
/
Build CLI Docker Image
Annotations
14 errors and 30 warnings
packages/services/policy/__tests__/policy.spec.ts > policy checks > should return empty result where there are not lint rules:
packages/services/policy/__tests__/policy.spec.ts#L22
AssertionError: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ packages/services/policy/__tests__/policy.spec.ts:22:27
|
packages/services/policy/__tests__/policy.spec.ts > policy checks > should return errors correctly:
packages/services/service-common/src/trpc.ts#L33
TRPCError: [
{
"code": "unrecognized_keys",
"keys": [
"require-nullable-result-in-root"
],
"path": [
"policy"
],
"message": "Unknown rule name passed"
}
]
❯ inputMiddleware node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:280:19
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ packages/services/service-common/src/trpc.ts:33:18
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ resolve node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:481:24
❯ packages/services/policy/__tests__/policy.spec.ts:26:20
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'BAD_REQUEST' }
Caused by: Caused by: ZodError: [
{
"code": "unrecognized_keys",
"keys": [
"require-nullable-result-in-root"
],
"path": [
"policy"
],
"message": "Unknown rule name passed"
}
]
❯ Object.get error [as error] node_modules/.pnpm/zod@3.23.8/node_modules/zod/lib/index.mjs:587:31
❯ ZodObject.parseAsync node_modules/.pnpm/zod@3.23.8/node_modules/zod/lib/index.mjs:715:22
❯ inputMiddleware node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:278:27
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ packages/services/service-common/src/trpc.ts:33:18
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ resolve node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:481:24
❯ packages/services/policy/__tests__/policy.spec.ts:26:20
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { issues: [ { code: 'unrecognized_keys', keys: [ 'require-nullable-result-in-root' ], path: [ 'policy' ], message: 'Unknown rule name passed' } ], addIssue: 'Function<anonymous>', addIssues: 'Function<anonymous>', errors: [ { code: 'unrecognized_keys', keys: [ 'require-nullable-result-in-root' ], path: [ 'policy' ], message: 'Unknown rule name passed' } ], format: 'Function<format>', isEmpty: false, flatten: 'Function<flatten>', formErrors: { formErrors: [], fieldErrors: { policy: [ 'Unknown rule name passed' ] } } }
|
packages/services/policy/__tests__/policy.spec.ts > policy checks > should return warnings correctly:
packages/services/service-common/src/trpc.ts#L33
TRPCError: [
{
"code": "unrecognized_keys",
"keys": [
"require-description"
],
"path": [
"policy"
],
"message": "Unknown rule name passed"
}
]
❯ inputMiddleware node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:280:19
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ packages/services/service-common/src/trpc.ts:33:18
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ resolve node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:481:24
❯ packages/services/policy/__tests__/policy.spec.ts:68:20
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'BAD_REQUEST' }
Caused by: Caused by: ZodError: [
{
"code": "unrecognized_keys",
"keys": [
"require-description"
],
"path": [
"policy"
],
"message": "Unknown rule name passed"
}
]
❯ Object.get error [as error] node_modules/.pnpm/zod@3.23.8/node_modules/zod/lib/index.mjs:587:31
❯ ZodObject.parseAsync node_modules/.pnpm/zod@3.23.8/node_modules/zod/lib/index.mjs:715:22
❯ inputMiddleware node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:278:27
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ packages/services/service-common/src/trpc.ts:33:18
❯ callRecursive node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:451:32
❯ resolve node_modules/.pnpm/@trpc+server@10.45.2/node_modules/@trpc/server/dist/index.mjs:481:24
❯ packages/services/policy/__tests__/policy.spec.ts:68:20
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { issues: [ { code: 'unrecognized_keys', keys: [ 'require-description' ], path: [ 'policy' ], message: 'Unknown rule name passed' } ], addIssue: 'Function<anonymous>', addIssues: 'Function<anonymous>', errors: [ { code: 'unrecognized_keys', keys: [ 'require-description' ], path: [ 'policy' ], message: 'Unknown rule name passed' } ], format: 'Function<format>', isEmpty: false, flatten: 'Function<flatten>', formErrors: { formErrors: [], fieldErrors: { policy: [ 'Unknown rule name passed' ] } } }
|
test / unit
Process completed with exit code 1.
|
tests/api/policy/policy-check.spec.ts > Schema policy checks > model: composite > Federation project with policy with only warnings, should check only the part that was changed:
integration-tests/tests/api/policy/policy-check.spec.ts#L78
AssertionError: expected [ 'ℹ Detected 1 change', '', …(5) ] to deeply equal [ 'ℹ Detected 1 change', '', …(10) ]
- Expected
+ Received
Array [
"ℹ Detected 1 change",
"",
" Safe changes:",
" - Field field was added to object type Query",
"",
- "",
- "⚠ Detected 1 warning",
- "",
- " - Description is required for type User (source: policy-require-description)",
- "",
"View full report:",
- Any<String>,
+ "http://localhost:8080/publiccitiesstayjoyously/hotpointsinventsafely/production/checks/534a8dfe-1850-4ef6-8303-0252f6e935eb",
]
❯ tests/api/policy/policy-check.spec.ts:78:35
|
tests/api/policy/policy-check.spec.ts > Schema policy checks > model: composite > Federation project with policy with , should check only the part that was changed:
integration-tests/testkit/cli.ts#L193
AssertionError: promise resolved "'ℹ Detected 1 change\n\n Safe change…'" instead of rejecting
- Expected:
[Error: rejected promise]
+ Received:
"ℹ Detected 1 change
Safe changes:
- Field field was added to object type Query
View full report:
http://localhost:8080/yummyparksdropyearly/calmpanscrypolitely/production/checks/fef2c558-ef42-4d65-b9f9-c9abde2c5316"
❯ Object.check testkit/cli.ts:193:23
❯ tests/api/policy/policy-check.spec.ts:132:26
|
tests/api/policy/policy-check.spec.ts > Schema policy checks > model: single > Single with policy with only warnings:
integration-tests/tests/api/policy/policy-check.spec.ts#L200
AssertionError: expected 'ℹ Detected 2 changes\n\n Safe chang…' to contain 'Detected 2 warnings'
- Expected
+ Received
- Detected 2 warnings
+ ℹ Detected 2 changes
+
+ Safe changes:
+ - Type User was added
+ - Field user was added to object type Query
+
+ View full report:
+ http://localhost:8080/niceringspullslowly/sixwallswinkrapidly/production/checks/25a980b6-dc6e-48b9-a900-ea685141b34c
❯ tests/api/policy/policy-check.spec.ts:200:23
|
tests/api/policy/policy-check.spec.ts > Schema policy checks > model: single > Single with policy with only errors:
integration-tests/testkit/cli.ts#L193
AssertionError: promise resolved "'ℹ Detected 2 changes\n\n Safe chang…'" instead of rejecting
- Expected:
[Error: rejected promise]
+ Received:
"ℹ Detected 2 changes
Safe changes:
- Type User was added
- Field user was added to object type Query
View full report:
http://localhost:8080/bigbathsfetchpolitely/wittysuitsfallknowlingly/production/checks/0d82418f-eeaa-4871-b3f5-6b59b104a426"
❯ Object.check testkit/cli.ts:193:23
❯ tests/api/policy/policy-check.spec.ts:233:26
|
tests/api/policy/policy-check.spec.ts > Schema policy checks > model: single > Single with policy with both errors and warning:
integration-tests/testkit/cli.ts#L193
AssertionError: promise resolved "'ℹ Detected 3 changes\n\n Safe chang…'" instead of rejecting
- Expected:
[Error: rejected promise]
+ Received:
"ℹ Detected 3 changes
Safe changes:
- Type User was added
- Field user was added to object type Query
- Field Query.foo is deprecated
View full report:
http://localhost:8080/luckyliesreplybravely/greatradioswarnhungrily/production/checks/9c4a5088-3dee-419a-b444-b8fc5aedd6b8"
❯ Object.check testkit/cli.ts:193:23
❯ tests/api/policy/policy-check.spec.ts:298:26
|
tests/api/policy/policy-crud.spec.ts > Policy CRUD > Project level > upserting a configuration works as expected on a project level:
integration-tests/tests/api/policy/policy-crud.spec.ts#L42
AssertionError: expected { Object (message) } to be null
❯ tests/api/policy/policy-crud.spec.ts:42:34
|
tests/api/policy/policy-crud.spec.ts > Policy CRUD > Project level > project level update is rejected when org does not allow to override:
integration-tests/tests/api/policy/policy-crud.spec.ts#L99
AssertionError: expected { Object (message) } to be null
❯ tests/api/policy/policy-crud.spec.ts:99:31
|
tests/api/policy/policy-crud.spec.ts > Policy CRUD > Org level > invalid rule config is rejected with an error:
integration-tests/tests/api/policy/policy-crud.spec.ts#L150
AssertionError: expected 'Validation error: Unknown rule name p…' to be 'Failed to validate rule "require-desc…' // Object.is equality
Expected: "Failed to validate rule "require-description" configuration: data/0 must NOT have additional properties"
Received: "Validation error: Unknown rule name passed at "config""
❯ tests/api/policy/policy-crud.spec.ts:150:43
|
tests/api/policy/policy-crud.spec.ts > Policy CRUD > Org level > empty rule config is rejected with an error:
integration-tests/tests/api/policy/policy-crud.spec.ts#L163
AssertionError: expected 'Validation error: Unknown rule name p…' to be 'Failed to validate rule "require-desc…' // Object.is equality
Expected: "Failed to validate rule "require-description" configuration: data/0 must NOT have fewer than 1 properties"
Received: "Validation error: Unknown rule name passed at "config""
❯ tests/api/policy/policy-crud.spec.ts:163:43
|
tests/api/policy/policy-crud.spec.ts > Policy CRUD > Org level > updating an org policy for the should upsert the policy record in the database:
integration-tests/tests/api/policy/policy-crud.spec.ts#L187
AssertionError: expected { Object (message) } to be null
❯ tests/api/policy/policy-crud.spec.ts:187:34
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
static-analysis / analyze (typescript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
static-analysis / analyze (typescript)
Unable to validate code scanning workflow: MissingPushHook
|
static-analysis / analyze (javascript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
static-analysis / analyze (javascript)
Unable to validate code scanning workflow: MissingPushHook
|
alpha / cli-test (ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Variables should be defined before their use:
docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/services.dockerfile#L22
UndefinedVar: Usage of undefined variable '$PORT'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/services.dockerfile#L13
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
docker/services.dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Legacy key/value format with whitespace separator should not be used:
docker/migrations.dockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Variables should be defined before their use:
docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
graphql-hive~console~EOMYP3+13.dockerbuild
|
2.22 MB |
|
graphql-hive~console~NGQR8B+13.dockerbuild
|
1.29 MB |
|
hive-cli-darwin-arm64
|
41.3 MB |
|
hive-cli-darwin-x64
|
42 MB |
|
hive-cli-linux-arm
|
41.8 MB |
|
hive-cli-linux-x64
|
46.6 MB |
|
hive-cli-win-x64
|
37 MB |
|
hive-cli-win-x86
|
34.4 MB |
|