[mc-nv]

What does the PR do?

• Declares license = "BSD-3-Clause" so METADATA carries a License-Expression field; the package previously shipped with no license metadata at all.
• Pins the previously unbounded hatchling requirement so emitted metadata does not depend on what the build environment resolves.

license-files is deliberately omitted because this repo has no LICENSE file — which is also why the add-license pre-commit hook is disabled here.

Where should the reviewer start?

pyproject.toml.

Test plan:

Verified: Metadata-Version 2.4 with License-Expression: BSD-3-Clause.

Related PRs:

• build: migrate tritonserver wheel to hatchling with PEP 639 metadata core#527
• build: migrate tritonfrontend wheel to hatchling with PEP 639 metadata server#8970
• build: migrate tritonclient wheel to hatchling with PEP 639 metadata client#927
• build: migrate model_analyzer to hatchling and pin the build backend model_analyzer#1038
• build: align perf_analyzer and genai-perf wheel metadata on PEP 639 perf_analyzer#469

Related Issues:

• Resolves: TRI-1775

^{CI (internal): [#67460724](http://tritonserver.local/ci/pipelines/67460724)}

[greptile-apps]

Confidence Score: 3/5

The PR is not yet safe to merge because request-controlled image downloads can still hold a synchronous preprocessing worker indefinitely.

Summary

• Adds License-Expression package metadata through license = "BSD-3-Clause".
• Pins the Hatchling build backend.
• Aligns CI with the pre-commit Ruff version.
• Adds image-download status checking, inactivity timeout, and size limiting, but lacks a total fetch deadline.

_{Reviews (2) · Last reviewed commit: "build: declare SPDX license and pin hatc..."}