Warning
also: warnings
A heads-up that something might become a problem. Unlike an error, it doesn't stop anything from working right now.
A non-fatal message from a compiler, linter, runtime, or library pointing to a likely problem, such as deprecated usage or risky code. Execution continues, but the underlying issue may become a bug or error later.
Your car's tire pressure light. You can still drive. Ignore it for a month, though, and you might end up with a flat on the highway.
Agents often say "the build passed with warnings." Some are harmless noise. Others are early signs of real bugs. Knowing the difference keeps you from ignoring the one that matters.
Build succeeded with 3 warnings: two unused imports, which are harmless, and one about a package feature that will be removed in the next major version.
The build shows warnings. List each one, say whether it's harmless or could cause a real problem, and fix only the risky ones.
Treating every warning as ignorable because the app still runs. A warning is often a bug that just hasn't happened yet.