chore: merge release/v0.3.0 back to main - #1291
Merged
Merged
Conversation
…k to v0.3.0] (#1263) Cherry-picks #1262 into the v0.3.0 release branch. #1262 landed on main after `release/v0.3.0` was cut, so it is not in the release branch. Its parent commit is the release branch tip (`16152fd4`), so this is a clean pick with no conflicts — the diff here is byte-identical to #1262. **Original:** fix(datasets): use fully qualified HF dataset ids (#1262) by @zhenchaoni Co-authored-by: Zhenchao Ni <zhenni@microsoft.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…erry-pick to v0.3.0] (#1267) Cherry-picks #1266 into the v0.3.0 release branch. This replaces pipe-backed native warning capture with a temporary-file spool, avoiding EP compiler hangs while preserving warning filtering and bounded memory use. Original commit: `e27a0faf` by @KayMKM. Cherry-picked cleanly onto release tip `e1d6f874` as `ce11819c`.
Release-window changes needed to build a correct v0.3.0 wheel. ### `chore(release): bump version to 0.3.0` (+ uv.lock sync) Bumps `pyproject.toml` (and `uv.lock`) to `0.3.0`. Version is exposed at runtime via `importlib.metadata`, so `pyproject.toml` is the only source. ### `ci(release): pin official build toolchain versions` `ModelKit Official Build` installed its toolchain with `pip install --upgrade build twine packaging` — completely unpinned. `build` 1.5.1 (released since v0.2.0) breaks the build inside the OneBranch container: ``` platformdirs\windows.py -> get_win_folder_from_registry winreg.QueryValueEx(key, CSIDL_LOCAL_APPDATA) -> FileNotFoundError: [WinError 2] The system cannot find the file specified ``` The sdist step fails and the wheel step is skipped, so the build produces nothing. Verified on run [153739315](https://dev.azure.com/microsoft/windows.ai.toolkit/_build/results?buildId=153739315) (failed, `build` 1.5.1) vs [150550609](https://dev.azure.com/microsoft/windows.ai.toolkit/_build/results?buildId=150550609) (v0.2.0, succeeded, `build` 1.5.0). `build` 1.5.0 and 1.5.1 have identical `_pip_env()`, so this is environment behavior in 1.5.1, not a change on our side. Pinning to the versions that produced v0.2.0 restores a green build and, more importantly, stops a third-party release from breaking the release build on publish day. Validated: official build [153740145](https://dev.azure.com/microsoft/windows.ai.toolkit/_build/results?buildId=153740145) succeeded on this branch — sdist, wheel, iKey verification, and PyPI validation all green. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
## Summary - Normalize PathLike model references before telemetry string scrubbing. - Prevent successful commands using local model paths from exiting with a Path.replace TypeError during telemetry reporting. - Add regression coverage for Click options parsed with path_type=Path. - Cherry-picked as a single focused commit onto release/v0.3.0. ## Validation - uv run pytest tests/unit/telemetry/test_click_group.py tests/unit/telemetry/test_utils_scrubbing.py -q (63 passed) - uv run ruff check src/winml/modelkit/telemetry/utils.py tests/unit/telemetry/test_click_group.py
## Summary - Treat TensorRT RTX like OpenVINO when validating Windows PDH GPU utilization. - Keep the benchmark, execution provider, device, adapter LUID, latency, and monitor structure assertions intact. - Document the unreliable PDH utilization behavior with a TODO in both ONNX-direct and Hugging Face GPU cases. ## Validation - `uv run --no-sync pytest -m e2e -q "tests/e2e/test_perf_e2e.py::TestPerfONNXDirect::test_benchmark_ep_device_gpu[nv_tensorrt_rtx]" "tests/e2e/test_perf_e2e.py::TestPerfHuggingFace::test_benchmark_ep_gpu[nv_tensorrt_rtx]" --basetemp=temp/pytest_tmp/release-v030-trtrtx-monitor-fix` (2 passed) - `uv run --no-sync ruff check --fix tests/e2e/test_perf_e2e.py`
Adds the v0.3.0 CHANGELOG entry, grouped by user-visible behavior changes, improvements, fixes, internals, and release assets.
xieofxie
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merges the published v0.3.0 release branch back to main. This brings the release-only fixes, v0.3.0 version and CHANGELOG entry, and the reproducible official-build toolchain pin into main.