Skip to content

pypi fixes for 0.2.1 patch release - #1081

Merged
chtruong814 merged 1 commit into
v0.2.0from
kajalj/patch-0.2.1-v6
Apr 15, 2026
Merged

chtruong814 merged 1 commit into
v0.2.0from
kajalj/patch-0.2.1-v6

Conversation

@kajalj22

Copy link
Copy Markdown
Contributor

Fixes known PyPI install compatibility issues.

  • Fixed ModuleNotFoundError: No module named 'scripts' on PyPI install
  • Moved ResourcesServerMetadata from scripts/ to nemo_gym.server_metadata
  • ng_init_resources_server templates are now bundled inside the package so they work from any current working directory
  • ng_init_resources_server now accepts relative paths (for example ../../resources_servers/my_server) and computes correct requirements.txt paths
  • ng_run resolves server directories from the current working directory first, then falls back to the install location for built-in servers. Local servers take priority
  • ng_collect_rollouts resolves input_jsonl_fpath from the current working directory, then the install location, so built-in example data works without copying files
  • Env vars for local testing
  • Github workflow for testing wheel gated by label
  • CVE package bumps
  • Added PyPI install documentation page

Test plan

fix: always send session cookie for starlette >= 1.0.0 (#942)

Bump version to 0.2.1 and make wheel test mandatory (#1065)

  • Makes the test-wheel-install CI job run on every PR by removing the conditional gate that required the test-wheel label or workflow_call trigger. This prevents broken wheels from being published again.

Replaces #1079 and #1080 (which had merge conflicts due to diverged package_info.py on the base branch).

Fixes known PyPI install compatibility issues.

- Fixed `ModuleNotFoundError: No module named 'scripts'` on PyPI install
- Moved `ResourcesServerMetadata` from `scripts/` to
`nemo_gym.server_metadata`
- `ng_init_resources_server` templates are now bundled inside the
package so they work from any current working directory
- `ng_init_resources_server` now accepts relative paths (for example
`../../resources_servers/my_server`) and computes correct
`requirements.txt` paths
- `ng_run` resolves server directories from the current working
directory first, then falls back to the install location for built-in
servers. Local servers take priority
- `ng_collect_rollouts` resolves `input_jsonl_fpath` from the current
working directory, then the install location, so built-in example data
works without copying files
- Env vars for local testing
- Github workflow for testing wheel gated by label
- CVE package bumps
- Added PyPI install documentation page

- Unit tests
- `ng_run` and `ng_collect_rollouts` with local editable install
(`reasoning_gym`)
- `ng_run` and `ng_collect_rollouts` with built-in PyPI server
(`arc_agi`)
- `ng_init`, `ng_run`, and `ng_collect_rollouts` with a new local server
alongside built-in agent and model
- `ng_init` with a relative path outside the repo (reproduces #936)

Bump version to 0.2.1 and make wheel test mandatory (#1065)

- Makes the `test-wheel-install` CI job run on **every PR** by removing
the conditional gate that required the `test-wheel` label or
`workflow_call` trigger. This prevents broken wheels from being
published again.

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

fix: always send session cookie for starlette >= 1.0.0 (#942)

Signed-off-by: cmunley1 <cmunley@nvidia.com>
Signed-off-by: Kajal Jain <kajalj@nvidia.com>
@kajalj22
kajalj22 requested a review from a team as a code owner April 15, 2026 20:34
@copy-pr-bot

copy-pr-bot Bot commented Apr 15, 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 marked this pull request as draft April 15, 2026 20:46
@chtruong814
chtruong814 marked this pull request as ready for review April 15, 2026 22:08
@chtruong814
chtruong814 merged commit 27e9211 into v0.2.0 Apr 15, 2026
6 checks passed
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.

2 participants