Deprecation of Jetpack 6.0 and 7.1 builds

[PawelPeczek-Roboflow]

What does this PR do?

We are removing stale builds of Jetpack.

Type of Change

• Other: Deprecation

Testing

• I have tested this change locally
• I have added/updated tests for this change

Test details:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation accordingly (if applicable)

Additional Context

[github-actions]

👋 Thanks for the pull request! Here is how automated Claude review works here, so you spend credits (and reviewer time) wisely.

🚦 This PR is marked Ready for review, so automated Claude review will run — and every pass spends real credits.

Warning

💸 The Claude reviewer bills in credits, not vibes

Automated review spins up a real agent that reads real code and spends real credits on every pass. It is glad to help — but it is not a rubber duck, a linter you poke in a loop, or a substitute for reading the contributing guide. Treat it like an expensive senior reviewer whose time you booked, and show up prepared.

Draft when unsure, Ready when you mean it:

• 🌱 Not sure the PR is in good shape yet? Keep it (or set it back) as a draft — drafts pause review, so you can push and iterate without burning credits on a moving target.
• 💪 Feel strong about the contents? Mark it Ready for review and the reviewer will take a look.

However you get there, arrive prepared:

• 🧱 Bring a SOLID, thorough PR. Point your local agent at our skills/ to tune it to our guidelines first — or, if you are one of those fabled carbon-based contributors, read them yourself. A half-baked diff costs exactly the same to review as a finished one.
• ✅ Resolve every comment before you re-request review. Re-requesting with threads still open means paying twice for the same conversation.
• 🔁 Do not use CI review as an inner loop for a local agent. The reviewer is not a step-by-step debugger — do the unfolding locally and arrive with the answer, not the search.
• 🙋 If something looks off, ask a human. One question to a maintainer is cheaper and faster than three rounds of agent re-review chasing a misread.

Reviews are not free. A draft costs nothing to review; a Ready PR is a promise that it is worth reviewing.

• Prefer to skip automated review entirely? Add the skip-claude-review label.

[github-actions]

🤖 Claude review started at commit 117365753dee0bd06f3c95b8dfdd9ea557eb19b6.

New commits are not auto-reviewed. Add the claude-review label to request a re-review — the label is consumed when the review starts, so just add it again next time.

[github-actions]

Skills: review-packaging-ci

Deprecation PR removing the JP6.0 build workflow and the JP6.0/JP7.1 Dockerfile.onnx.jetson.* files. I traced the remaining references to the deleted paths.

Medium — orphaned test workflow references the deleted JP6.0 Dockerfile

.github/workflows/test.jetson_6.0.0.yml is not removed by this PR, but at line 38 it still runs:

docker build -t roboflow/roboflow-inference-server-jetson-6.0.0:test -f docker/dockerfiles/Dockerfile.onnx.jetson.6.0.0 .

Since docker/dockerfiles/Dockerfile.onnx.jetson.6.0.0 is deleted here, this step now fails with "no such file or directory" whenever the workflow is dispatched. It is workflow_dispatch-only on a self-hosted jetpack-6.0.0 runner, so it does not break merge CI — but it leaves a broken JP6.0 regression job behind. To make the deprecation complete, delete test.jetson_6.0.0.yml in this PR as well (mirroring the docker.jetson.6.0.0.yml removal).

Minor doubts (non-blocking)

• inference_cli/lib/container_adapter.py still routes L4T 36.x (JP6.0/6.1) to jetson-6.0.0:latest and L4T 38.x (JP7.1) to jetson-7.1.0:latest. After deprecation these tags stop receiving updates (6.0 image still exists on Docker Hub; 7.1 had no build workflow). This is pre-existing and likely an intended follow-up, but worth confirming whether the CLI mapping should redirect deprecated Jetpacks to a supported image.
• .github/workflows/docker.inference_server.yml still offers a jetson_6_0_0 matrix entry pointing at inference_server/docker/Dockerfile.jetson.6.0.0 — a different (currently non-existent) path, unrelated to these deletions.

Reviewed at HEAD: 1173657