Maintenance Notes

Maintenance Notes

Evidence-backed notes that explain current dashboard state, intentional platform limits, or follow-up work. Keep transient progress in upstream issues or PRs; add notes here only when they affect a row in Feedstock Inventory.

• Home
• Feedstock Inventory
• Dashboard Conventions

Created Feedstocks

• momentum-feedstock PR #293 for the CUDA 13 migration has merged at 4e8a191 from head bba9286. It landed the short-term eigen >=3.4,<4 workaround for current Momentum 0.1.110, the Linux CUDA 13 cuda-gdb skip for Python 3.13/3.14, and the runtime Eigen dependency needed by downstream momentum-cpp CMake consumers. The longer-term Eigen 5 support follow-up remains upstream in facebookresearch/momentum#1407 and facebookresearch/momentum#1408.
• momentum-feedstock PR #295 has merged at 6592853 and uploaded linux-aarch64 artifacts for momentum 0.1.110; the row now includes la64 and remains yellow only because linux-ppc64le artifacts are not present.
• momentum-feedstock PR #300 was the tbb 2023 bot rebuild. The first Azure run failed before the recipe ran because the worker could not resolve pixi.sh; the branch was no-op amended to 2ac4b56 to restart CI without adding a PR comment. It merged as 15cfb22.
• momentum-feedstock PR #301 is ready for review at e30ebe9, rebased on #300. The pre-ready current-head GitHub/Azure/linter CI was green, and converting from draft to ready started a fresh Azure matrix build 1544055 on the same head. It reflects upstream PyPI split work from facebookresearch/momentum#1483, #1523, and #1503 by adding a real pymomentum-core output, making pymomentum-cpu/pymomentum-gpu real full-package outputs, and keeping pymomentum as a compatibility metapackage. pymomentum-cpu/pymomentum-gpu were already registered through conda-forge/admin-requests#1137; conda-forge/admin-requests#2165 registered the new pymomentum-core output. Do not merge before 2026-06-26 08:37 PT / 2026-06-26 15:37 UTC; leave the 24h reviewer window open and avoid PR comments unless asked.
• mhr-feedstock PR #5 merged as cccb284 for mhr 1.0.1 with recipe/pyproject-runtime-deps.patch to backport the missing NumPy runtime metadata. Upstream facebookresearch/MHR#71 has merged the same fix, but the latest public GitHub/PyPI/conda release remains 1.0.1, which predates it. On the next upstream release containing #71, remove the feedstock patch and the source.patches entry instead of carrying the backport forward.
• pyroomacoustics-feedstock was created and PRs #1, #4, and #5 have merged. Build 3 artifacts for pyroomacoustics 0.8.3 are uploaded for linux-64, linux-aarch64, linux-ppc64le, osx-64, osx-arm64, and win-64; the recipe is now v1 and the row is green.
• mmpose-feedstock PR #7 and mmpretrain-feedstock PR #4 have merged and uploaded noarch: python artifacts. The packages are platform-independent, while mmcv/pytorch dependency availability still controls where installs solve.
• drjit-cpp-feedstock PR #45 is the bot drjit-cpp 1.4.0 update. The original bot head b678c1b failed before builds because recipe/patches/drjit/0005-Allow-disabling-python-stubs.patch no longer applied after upstream Dr.Jit added Metal Python install/stub entries in v1.4.0; the branch was updated to e72c97a with the patch refreshed to keep .py installs outside DRJIT_ENABLE_STUBS while gating .pyi and py.typed, including drjit/metal. The e72c97a CI then failed because Dr.Jit v1.4.0 expected newer vendored submodule commits than the bot-updated recipe still pinned, and Linux CPU C++ also exposed DRJIT_ENABLE_OPTIX defaulting on while CUDA was off. The afe01f7 CI fixed those but exposed the new macOS Metal backend failing against conda-forge's macOS 11 SDK (MTLResourceID, gpuAddress, MTLGPUFamilyMetal3, and related APIs are not available). The PR branch is now 02b5526, which updates the vendored Dr.Jit submodule source archives to the upstream v1.4.0 pins, refreshes drjit-core/disable-march-flags.patch for the newer cmake-defaults, gates DRJIT_ENABLE_OPTIX with CUDA in C++ and Python builds, and disables DRJIT_ENABLE_METAL for macOS builds until conda-forge uses a newer SDK. Current-head CI is green: GitHub Actions run 28258093104, Azure build 1544722, and the linter all passed on 02b5526. After #45 merges, consider a separate follow-up PR to re-enable Metal via a newer conda-forge macOS SDK or an upstream compatibility guard; do not mix that investigation into the current bot version update. No existing patch could be cleanly removed for this upstream release; the source-stub and ISA patches still cover feedstock-specific build constraints. Local validation covered manual application of all source patches to the v1.4.0 tree, conda-smithy recipe-lint --conda-forge recipe, conda-smithy rerender --check --feedstock_directory ., git diff --text --check, a full Linux CPU C++ build without tests, a full Linux CPU Python 3.12 build without tests, representative Linux CUDA 12.9 C++/Python render-only checks, and representative osx-arm64 C++ / osx-64 Python render-only checks. Avoid public PR comments unless asked; do not merge unless explicitly requested.
• Remaining yellow created feedstocks are currently intentional platform limits unless noted above: igl, gpytoolbox, and pymeshlab are blocked from linux-ppc64le by the Embree/libigl dependency surface; causal-conv1d, gsplat, nerfacc, and tiny-cuda-nn are CUDA/PyTorch extension packages where macOS and linux-ppc64le are not applicable and Windows remains disabled until the conda-forge PyTorch/CUDA extension build path is proven; inplace-abn keeps Windows and some CUDA/Python variants skipped per recipe comments.

Co-Maintained Feedstocks

• igl-feedstock PR #51 merged as 9ed0532 to add linux-aarch64; all five linux-aarch64 artifacts for 2.6.1 are uploaded. Local linux-aarch64 Python 3.12 --no-test build completed successfully after the cross-compile stubgen fix. linux-ppc64le was removed after CI showed the upstream Embree-backed build passes -msse2, which the ppc64le compiler rejects.
• librerun-sdk-feedstock is already on v1 recipe.yaml with conda_build_tool: rattler-build on main; no conversion PR is needed.
• rerun-sdk-feedstock has a local v1/rattler-build migration prepared and validated, but the PR should be opened after the Wayland unblock PR #120 lands so the modernization stays separate from the functional fix.