Skip to content

chore: sync ROCm lock track with the 1.9.0 pin and record dual-track dependency governance - #2432

Merged
TATP-233 merged 1 commit into
mainfrom
chore/rocm-lock-sync-governance
Oct 19, 2026
Merged

TATP-233 merged 1 commit into
mainfrom
chore/rocm-lock-sync-governance

Conversation

@TATP-233

Copy link
Copy Markdown
Collaborator

Summary

Follow-up to #2431 (which landed on main before this commit was pushed):

  • pyproject.rocm.toml: bump unisim-core 1.7.22 → 1.9.0 (base + motrix extras), catching up with the main pin from feat!: consume torch-first unisim DR payloads (#2410) #2431.
  • uv.rocm.lock: regenerated under the ROCm config; uv lock --check clean.
  • Governance: dependency pin changes must keep the ROCm track in sync (same bump to pyproject.rocm.toml + regenerated uv.rocm.lock in the same PR) — recorded in docs/sphinx/source/{en,zh_CN}/4-developer_guide/5-contributing_workflow.md (PR 与 CI section) and AGENTS.md / CLAUDE.md Validation sections.

Validation

  • uv lock --check under the ROCm config (pyproject.rocm.toml + uv.rocm.lock swapped in): clean
  • uv run pytest tests/scripts/test_check_docs.py -q: 20 passed
  • No runtime code changed; main pyproject.toml / uv.lock untouched.

…dependency governance

- pyproject.rocm.toml: bump unisim-core to 1.9.0 (base + motrix extras)
  and regenerate uv.rocm.lock under the ROCm config (uv lock --check clean)
- Workflow policy: dependency pin changes must update both lock tracks
  (uv.lock + pyproject.rocm.toml/uv.rocm.lock) in the same PR, listed in
  the PR evidence; published-dependency transitions require the upstream
  PyPI release first (en/zh_CN 5-contributing_workflow.md, AGENTS.md,
  CLAUDE.md)
@TATP-233
TATP-233 merged commit 625e01f into main Oct 19, 2026
8 checks passed
@TATP-233
TATP-233 deleted the chore/rocm-lock-sync-governance branch October 19, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant