chore(deps): update dependency express to v4.21.1 #15109
pr.yaml
on: pull_request
build
/
build-and-dockerize
29m 41s
alpha
/
cli-artifacts
6m 28s
alpha
/
...
/
snapshot
1m 24s
graphql-breaking-changes
/
search-token
0s
db-types
/
diff
1m 44s
test
/
db-migrations
1m 57s
test
/
unit
3m 49s
code-style
/
eslint-and-prettier
7m 48s
typescript
/
typecheck
6m 8s
website-preview
/
deployment
7s
storybook-preview
/
deployment
8s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
test
/
e2e
3m 20s
Matrix: test / integration
Matrix: alpha / cli-test
graphql-breaking-changes
/
check
8s
alpha
/
...
/
Build CLI Docker Image
Annotations
38 warnings
alpha / npm / snapshot
Failed to restore: Cache service responded with 429
|
alpha / npm / snapshot
The following actions use a deprecated Node.js version and will be forced to run on node20: the-guild-org/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
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/
|
db-types / diff
Failed to restore: Cache service responded with 429
|
test / db-migrations
Failed to restore: Cache service responded with 429
|
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)
Failed to restore: Cache service responded with 429
|
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)
Failed to restore: Cache service responded with 429
|
test / unit
Failed to restore: Cache service responded with 429
|
typescript / typecheck
Failed to restore: Cache service responded with 429
|
alpha / cli-artifacts
Failed to restore: Cache service responded with 429
|
alpha / cli-artifacts
Failed to restore: Cache service responded with 429
|
code-style / eslint-and-prettier
Failed to restore: Cache service responded with 429
|
code-style / eslint-and-prettier
Failed to restore: Cache service responded with 429
|
build / build-and-dockerize
Failed to restore: Cache service responded with 429
|
build / build-and-dockerize
Failed to restore: Cache service responded with 429
|
build / build-and-dockerize
The following actions uses node12 which is deprecated and will be forced to run on node16: vimtor/action-zip@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build / build-and-dockerize
The following actions use a deprecated Node.js version and will be forced to run on node20: vimtor/action-zip@v1, randomairborne/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
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/
|
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#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#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/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#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#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/migrations.dockerfile#L12
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/
|
test / e2e
Failed to restore: Cache service responded with 429
|
test / integration (3)
Failed to restore: Cache service responded with 429
|
test / integration (3)
Failed to restore: Cache service responded with 429
|
test / integration (2)
Failed to restore: Cache service responded with 429
|
test / integration (2)
Failed to restore: Cache service responded with 429
|
test / integration (1)
Failed to restore: Cache service responded with 429
|
test / integration (1)
Failed to restore: Cache service responded with 429
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
graphql-hive~platform~SX53LC+13.dockerbuild
|
1.39 MB |
|
hive-cli-darwin-arm64
|
39.6 MB |
|
hive-cli-darwin-x64
|
40.3 MB |
|
hive-cli-linux-arm
|
40.1 MB |
|
hive-cli-linux-x64
|
44.8 MB |
|
hive-cli-win-x64
|
35.2 MB |
|
hive-cli-win-x86
|
32.7 MB |
|