fix(storage): added missing index for targets.project_id
#17232
pr.yaml
on: pull_request
Matrix: build / build-and-dockerize
alpha
/
cli-artifacts
4m 49s
alpha
/
...
/
snapshot
51s
graphql-breaking-changes
/
search-token
0s
db-types
/
diff
1m 2s
test
/
db-migrations
1m 18s
test
/
unit
1m 50s
code-style
/
eslint-and-prettier
3m 26s
typescript
/
typecheck
4m 22s
website-preview
/
deployment
5s
storybook-preview
/
deployment
10s
release-candidate
/
snapshot
Matrix: static-analysis / analyze
Matrix: alpha / cli-test
graphql-breaking-changes
/
check
10s
test
/
e2e
3m 14s
Matrix: test / integration
alpha
/
...
/
Build CLI Docker Image
Annotations
6 errors and 29 warnings
db-types / diff
Process completed with exit code 1.
|
test / e2e
Process completed with exit code 1.
|
test / integration (2)
Process completed with exit code 1.
|
test / integration (1)
Process completed with exit code 1.
|
test / integration (3)
The job was canceled because "_2" failed.
|
test / integration (3)
The operation was canceled.
|
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/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/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/
|
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/
|
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/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#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/
|
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/
|
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#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/
|
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/
|
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/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/
|
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#L22
UndefinedVar: Usage of undefined variable '$PORT'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
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/
|
test / e2e
No files were found with the provided path: ./cypress/videos/**/*
./cypress/screenshots/**/*. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
graphql-hive~console~MTU62G+13.dockerbuild
|
1.12 MB |
|
graphql-hive~console~W3OCJ6+13.dockerbuild
|
2.53 MB |
|
hive-cli-darwin-arm64
|
42.3 MB |
|
hive-cli-darwin-x64
|
43 MB |
|
hive-cli-linux-arm
|
42.8 MB |
|
hive-cli-linux-x64
|
47.6 MB |
|
hive-cli-win-x64
|
37.9 MB |
|
hive-cli-win-x86
|
35.4 MB |
|