PR #7859 merged without successful status checks (mapbox-navigation-android)

[mapbox-github-ci-issues-1]

👋 Hey there! It's Changebot, and I help repositories follow our engineering best practices. My magic wand found some things I wanted to highlight for your review:

Item	Current status	Required?	Best practice guidelines
Run unsuccessful: ci/circleci: release-workflow/release-snapshot-start	pending	optional	success
Run unsuccessful: ci/circleci: default/mobile-metrics-dry-run	pending	optional	success
Run unsuccessful: ci/circleci: assemble	pending	optional	success
Run unsuccessful: ci/circleci: unit-tests-core	pending	optional	success
Run unsuccessful: ci/circleci: changelog-verification	pending	optional	success
Run unsuccessful: ci/circleci: ui-robo-tests	pending	optional	success
Run unsuccessful: ci/circleci: unit-tests-androidauto	pending	optional	success
Run unsuccessful: ci/circleci: assemble-instrumentation-test	pending	optional	success
Run unsuccessful: Prisma Cloud / Code analysis	pending	optional	success
Run unsuccessful: ci/circleci: assemble-instrumentation-test-internal	pending	optional	success
Run unsuccessful: ci/circleci: assemble-old-deps-compat	pending	optional	success
Run unsuccessful: ci/circleci: assemble-app-mincompile	pending	optional	success
Run unsuccessful: ci/circleci: prepare-static-analysis	pending	optional	success
Run unsuccessful: Analyze (python)	null	optional	success
Run unsuccessful: Analyze (java)	null	optional	success
Run unsuccessful: process	null	optional	success
Run unsuccessful: process	skipped	optional	success
Run unsuccessful: publisher-deployer	neutral	optional	success
Run unsuccessful: default	null	optional	success
Run unsuccessful: release-workflow	null	optional	success

The following PR was merged without the status checks passing: #7859

Can you take a look at these best practices and make any adjustments if needed?

Please tag @mapbox/security-and-compliance on this issue if you have any questions