docs: add documentation for upstream reliability (retry + timeout) #16733
pr.yaml
on: pull_request
Matrix: build / build-and-dockerize
alpha
/
cli-artifacts
4m 48s
alpha
/
...
/
snapshot
2m 7s
graphql-breaking-changes
/
search-token
0s
db-types
/
diff
1m 13s
test
/
db-migrations
1m 24s
test
/
unit
1m 59s
code-style
/
eslint-and-prettier
3m 17s
typescript
/
typecheck
4m 13s
website-preview
/
deployment
4m 0s
storybook-preview
/
deployment
8s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
Matrix: alpha / cli-test
graphql-breaking-changes
/
check
8s
test
/
e2e
4m 24s
Matrix: test / integration
alpha
/
...
/
Build CLI Docker Image
Annotations
30 warnings
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 (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
|
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
|
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/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#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/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#L12
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#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#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/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/
|
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/
|
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#L14
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/
|
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/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#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/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#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/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~KKXMKW+13.dockerbuild
|
1.63 MB |
|
graphql-hive~console~N7HY6S+13.dockerbuild
|
2.25 MB |
|
hive-cli-darwin-arm64
|
41.3 MB |
|
hive-cli-darwin-x64
|
42 MB |
|
hive-cli-linux-arm
|
41.9 MB |
|
hive-cli-linux-x64
|
46.6 MB |
|
hive-cli-win-x64
|
36.9 MB |
|
hive-cli-win-x86
|
34.4 MB |
|