Skip to content
Lint, Build, Test, Publish

Publish #827

Sign in to view logs

Publish

Publish #827

Triggered via push January 22, 2024 18:34
@AkiyamkaAkiyamka
pushed 2de6758
@konturio/[email protected]
Status Failure
Total duration 1m 34s
Artifacts –

build.yml

on: push
build
1m 27s
build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
build
Process completed with exit code 1.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-regex-match@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build: cosmos/index.tsx#L10
Forbidden non-null assertion
build: cosmos/index.tsx#L12
Unexpected console statement
build: packages/floating/src/Tooltip/TooltipTrigger.tsx#L10
Unexpected any. Specify a different type
build: packages/floating/src/Tooltip/TooltipTrigger.tsx#L15
Unexpected any. Specify a different type
build: packages/floating/src/Tooltip/TooltipTrigger.tsx#L17
React Hook React.useLayoutEffect has missing dependencies: 'context.refs' and 'propRef'. Either include them or remove the dependency array
build: packages/floating/src/Tooltip/fixtures/MapTooltip.fixture.tsx#L11
Do not use "@ts-ignore" because it alters compilation errors
build: packages/floating/src/Tooltip/fixtures/MapTooltip.fixture.tsx#L19
Do not use "@ts-ignore" because it alters compilation errors
build: packages/floating/src/Tooltip/fixtures/MapTooltip.fixture.tsx#L52
Include a description after the "@ts-expect-error" directive to explain why the @ts-expect-error is necessary. The description must be 3 characters or longer
build: packages/ui-kit/src/Autocomplete/components/AutocompleteItem/index.tsx#L10
Unexpected any. Specify a different type
build: packages/ui-kit/src/Autocomplete/fixtures/Autocomplete.fixture.tsx#L19
Unexpected console statement