Skip to content

Bump transformers, mlflow, hydra-core, sqlparse for CVE fixes - #2982

Merged
kajalj22 merged 3 commits into
NVIDIA-NeMo:mainfrom
kajalj22:kajalj/bump-cve-sep2026
Sep 4, 2026
Merged

kajalj22 merged 3 commits into
NVIDIA-NeMo:mainfrom
kajalj22:kajalj/bump-cve-sep2026

Conversation

@kajalj22

@kajalj22 kajalj22 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • transformers: >=5.8.1 -> >=5.15.1 (stirrup_agent requirements.txt)
  • mlflow / mlflow-skinny: >=3.15.1 -> >=3.15.2
  • hydra-core: unpinned -> >=1.3.5 (resolves to 1.3.6)
  • sqlparse: added explicit >=0.6.0 pin (transitive via mlflow-skinny, whose own constraint <1,>=0.4.0 wouldn't pull the fix)

Test plan

  • uv lock regenerated successfully, resolved versions confirmed (hydra-core 1.3.6, mlflow/mlflow-skinny 3.15.2, sqlparse 0.6.0)

- transformers>=5.8.1 -> >=5.15.1
- mlflow / mlflow-skinny >=3.15.1 -> >=3.15.2
- hydra-core (unpinned) -> >=1.3.5
- sqlparse pinned explicitly to >=0.6.0 (transitive via mlflow-skinny)

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
@kajalj22
kajalj22 requested a review from a team as a code owner September 2, 2026 18:55
@copy-pr-bot

copy-pr-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@kajalj22 kajalj22 added the r0.6.0 Auto-cherrypick to release branch. Apply before merge; cherrypick happens after merge. label Sep 2, 2026
@kajalj22
kajalj22 requested a review from ananthsub September 2, 2026 19:00
@kajalj22

kajalj22 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 9907d6b

ananthsub
ananthsub previously approved these changes Sep 2, 2026
resources_servers/vlm_eval_kit pins omegaconf>=2.4.0.dev4. hydra-core
1.3.2+ caps omegaconf<2.4, but 1.3.0 only requires omegaconf~=2.2 (up
to <3.0), which is what let that server's isolated venv resolve before.
Adding the >=1.3.5 floor blocked the fallback to 1.3.0 and made that
server's dependency resolution unsatisfiable.

Leaving hydra-core unpinned still locks the root project to 1.3.6
(uv picks newest-compatible by default), which is the CVE-fixed
version, while letting vlm_eval_kit fall back to 1.3.0 as before.

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
@kajalj22

kajalj22 commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 57017a5

@kajalj22
kajalj22 merged commit 9cca63c into NVIDIA-NeMo:main Sep 4, 2026
37 checks passed
kajalj22 added a commit that referenced this pull request Sep 4, 2026
…982)` into `r0.6.0` (#3088)

beep boop [πŸ€–]: Hi @kajalj22 πŸ‘‹,

    we've cherry picked #2982 into  for you! πŸš€

    Please review and approve this cherry pick by your convenience!

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Signed-off-by: NeMo Bot <nemo-bot@nvidia.com>
Co-authored-by: kajalj22 <kajalj@nvidia.com>
jkyi-nvidia pushed a commit that referenced this pull request Sep 11, 2026
## Summary
- `transformers`: `>=5.8.1` -> `>=5.15.1` (stirrup_agent
requirements.txt)
- `mlflow` / `mlflow-skinny`: `>=3.15.1` -> `>=3.15.2`
- `hydra-core`: unpinned -> `>=1.3.5` (resolves to 1.3.6)
- `sqlparse`: added explicit `>=0.6.0` pin (transitive via
mlflow-skinny, whose own constraint `<1,>=0.4.0` wouldn't pull the fix)

## Test plan
- [x] `uv lock` regenerated successfully, resolved versions confirmed
(hydra-core 1.3.6, mlflow/mlflow-skinny 3.15.2, sqlparse 0.6.0)

---------

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Signed-off-by: Junkeun Yi <jkyi@nvidia.com>

This branch was previously deployed

1 inactive deployment
public β€” 57017a5d Deployed Sep 3, 2026 by copy-pr-bot[bot] via release / finalize / notify #2507
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

r0.6.0 Auto-cherrypick to release branch. Apply before merge; cherrypick happens after merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants