chore(devtools): upgrade ods: v0.6.1->v0.6.2 (#8773) to release v2.12

[nmgarza5]

Cherry-pick of commit e5ebb45 to release/v2.12 branch.

Original PR: #8773

• [Optional] Override Linear Check

---

Summary by cubic

Upgraded onyx-devtools to 0.6.2 for the v2.12 release. Aligns dev tooling with the latest fixes and has no runtime impact.

• Dependencies
  • Bumped onyx-devtools from 0.5.1 to 0.6.2 in backend/requirements/dev.txt and pyproject.toml.
  • Updated uv.lock to reflect the new version.

^{Written for commit 6c34d90. Summary will update on new commits.}

[greptile-apps]

Greptile Summary

This PR cherry-picks a onyx-devtools (ods) version bump to the release/v2.12 branch. It updates the package in pyproject.toml, backend/requirements/dev.txt, and uv.lock.

Key observations:

• onyx-devtools is a dev-only dependency (gated behind the dev extras marker), so this change carries no production risk.
• Although the original PR (chore(devtools): upgrade ods: v0.6.1->v0.6.2 #8773) title describes a patch upgrade (v0.6.1 → v0.6.2), the actual net change on the release/v2.12 branch is v0.5.1 → v0.6.2 — a jump of two minor versions — because this branch had not received the earlier 0.5.x → 0.6.1 bump yet. The cherry-picked commit is correct, but reviewers should be aware that the effective delta on this branch is larger than the title implies.
• All wheel URLs and SHA256 hashes in uv.lock have been updated consistently across every supported platform (any, macOS x86/arm64, manylinux aarch64/x86_64, win amd64/arm64).

Confidence Score: 5/5

• This PR is safe to merge — it only bumps a dev-only dependency with no production impact.
• All three changed files are purely mechanical: a version string update in pyproject.toml, the pinned requirements file, and the lock file. onyx-devtools is scoped exclusively to the dev extras group, so it cannot affect any production runtime. The lock file hashes are consistent across all platforms. The only noteworthy point is that the effective version jump on this branch (0.5.1 → 0.6.2) is larger than the PR title implies, but given the dev-only scope this poses minimal risk.
• No files require special attention.

Important Files Changed

Filename	Overview
backend/requirements/dev.txt	Single line change bumping onyx-devtools from 0.5.1 to 0.6.2 — dev-only dependency, no production impact.
pyproject.toml	Single line change bumping onyx-devtools from 0.5.1 to 0.6.2 in the dev extras group.
uv.lock	Lock file updated with new wheel URLs and SHA256 hashes for onyx-devtools 0.6.2 across all platforms; hashes appear consistent.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release/v2.12 branch\nonyx-devtools == 0.5.1] -->|cherry-pick of original PR #8773| B[onyx-devtools == 0.6.2]
    C[main branch\nonyx-devtools == 0.6.1] -->|original PR #8773| D[onyx-devtools == 0.6.2]

    style A fill:#f9a825,color:#000
    style B fill:#43a047,color:#fff
    style C fill:#1e88e5,color:#fff
    style D fill:#43a047,color:#fff

Loading

_{Last reviewed commit: 6c34d90}

[cubic-dev-ai]

1 issue found across 3 files

Confidence score: 4/5

• The only concern is a process/source-of-truth issue: editing backend/requirements/dev.txt directly may be overwritten because it’s generated from pyproject.toml/uv.lock.
• Impact is likely limited to dependency drift rather than runtime breakage, so this looks safe to merge once the source-of-truth update path is confirmed.
• Pay close attention to backend/requirements/dev.txt - generated file should be updated via pyproject.toml/lock regeneration to avoid being overwritten.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="backend/requirements/dev.txt">

<violation number="1" location="backend/requirements/dev.txt:320">
P2: This requirements file is generated and should not be edited directly. Update `pyproject.toml` (and regenerate `uv.lock`/requirements) instead; otherwise this change will be overwritten and the source-of-truth dependencies will remain unchanged.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: This requirements file is generated and should not be edited directly. Update pyproject.toml (and regenerate uv.lock/requirements) instead; otherwise this change will be overwritten and the source-of-truth dependencies will remain unchanged.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At backend/requirements/dev.txt, line 320:

<comment>This requirements file is generated and should not be edited directly. Update `pyproject.toml` (and regenerate `uv.lock`/requirements) instead; otherwise this change will be overwritten and the source-of-truth dependencies will remain unchanged.</comment>

<file context>
@@ -317,7 +317,7 @@ oauthlib==3.2.2
     #   kubernetes
     #   requests-oauthlib
-onyx-devtools==0.5.1
+onyx-devtools==0.6.2
     # via onyx
 openai==2.14.0
</file context>