Fix cleanup guard behavior and standardize workspace check scripts #137
TrueNinepull-request.yml
on: pull_request
release-preflight
14s
gui-release-preflight
6s
build
2m 59s
lint
2m 3s
check-type
2m 25s
test
3m 29s
test-sdk
2m 30s
test-cli
2m 53s
test-mcp
2m 18s
test-libraries
1m 40s
test-rust
1m 58s
Annotations
10 errors and 1 warning
|
lint:
sdk/test/native-binding/cleanup.ts#L398
Unsafe member access .debug on a type that cannot be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L398
Unsafe call of a type that could not be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L382
Unsafe member access .debug on a type that cannot be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L382
Unsafe call of a type that could not be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L360
Unsafe member access .warn on a type that cannot be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L360
Unsafe call of a type that could not be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L175
Unsafe assignment of an error typed value
|
|
lint:
sdk/test/native-binding/cleanup.ts#L169
Unsafe assignment of an error typed value
|
|
lint:
sdk/test/native-binding/cleanup.ts#L165
Unsafe member access .error on a type that cannot be resolved
|
|
lint:
sdk/test/native-binding/cleanup.ts#L165
Unsafe call of a type that could not be resolved
|
|
lint:
doc/components/home-contributors.tsx#L478
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|