Skip to content
CI

Add Kotlin (build.gradle.kts) snippet to Android NDK link-libraries docs #49221

Sign in to view logs

Add Kotlin (build.gradle.kts) snippet to Android NDK link-libraries docs

Add Kotlin (build.gradle.kts) snippet to Android NDK link-libraries docs #49221

Re-run triggered June 26, 2026 22:55
@coolguyzonecoolguyzone
#18493
gords2:android-ndk-gradle-kts
Status Success
Total duration 1m 6s
Artifacts –

test.yml

on: pull_request
Lint
1m 1s
Lint
Check Typos
12s
Check Typos
Test
43s
Test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
Lint
[@octokit/auth-app] appId option is required
Lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: getsentry/action-github-app-token@97c9e23528286821f97fba885c1b1123284b29cc. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Lint: src/components/home.tsx#L335
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
Lint: src/components/home.tsx#L264
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
Lint: src/components/home.tsx#L191
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
Lint: src/components/home.tsx#L66
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
Lint: src/components/featureInfo.tsx#L142
Do not use an `<a>` element to navigate to `/product/explore/metrics/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Lint: src/components/featureInfo.tsx#L126
Do not use an `<a>` element to navigate to `/product/user-feedback/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Lint: src/components/featureInfo.tsx#L110
Do not use an `<a>` element to navigate to `/product/explore/profiling/profile-details/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Lint: src/components/featureInfo.tsx#L93
Do not use an `<a>` element to navigate to `/product/explore/logs/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Lint: src/components/featureInfo.tsx#L57
Do not use an `<a>` element to navigate to `/product/sentry-basics/distributed-tracing/generate-first-error/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Lint: src/components/featureInfo.tsx#L37
Do not use an `<a>` element to navigate to `/product/sentry-basics/integrate-frontend/generate-first-error/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages