openusd v26.05

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/24960412913 - please use this URL for debugging.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[traversaro]

What do you think @ndeybach, do you think we can merge?

[ndeybach]

Hi @traversaro,

Sorry for the delay.

I think after reading at the changelog that there doesn't seem to be something build breaking.

I would only have a point of improvement regarding the PR I did last time. I am currently working on the OIIO feedstock on a major upgrade with staging approach used. And h-vetinari pointed (rightly so) to my wrong pins based on cmake. So last time the pin I did on :
- libopensubdiv 3.*

was wrong from the pov of the conda forge guidelines, as it could block auto upgrades apparently. Especially as libopensubdiv has run exports, so we can / should just rely on those and it should never use the cmake lower bounds anyway.

So from my pov it should be mergeable since tests are also passing once this pin is removed. But I am not using openusd too much (only linking to 2 headers), so you would probably be better than me for the final call.

I can do a PR for the pin if you want (Still hesitant to add myself here as maintainer since I do not use openusd widely or a lot for now, but if you think I can still help I can do a PR demand for it to simplify such modifications in future).

---

And on the side of the refactor we discussed last time, I am still finishing the oiio / ocio feedstock upgrade with the new staging CEP. I will probably start working on openusd in a few weeks once I am done there and the recipe is validated a bit with review / feedback / no issues. So I would not block this upgrade for that. Especially as we should probably do a build increase for the change anyway.

[traversaro]

was wrong from the pov of the conda forge guidelines, as it could block auto upgrades apparently. Especially as libopensubdiv has run exports, so we can / should just rely on those and it should never use the cmake lower bounds anyway.

Considering there was never a non 3.* release of libopensubdiv on conda-forge, I do not think this is a big problem, but yes let's remove the 3.* .

I will probably start working on openusd in a few weeks once I am done there and the recipe is validated a bit with review / feedback / no issues. So I would not block this upgrade for that. Especially as we should probably do a build increase for the change anyway.

Great, thanks!

[traversaro]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

• ℹ️ azure.settings_win.variables.MINIFORGE_HOME is deprecated, please use workflow_settings.tools_install_dir instead.
• ℹ️ azure.settings_win.variables.CONDA_BLD_PATH is deprecated, please use workflow_settings.build_workspace_dir instead.
• ℹ️ 'Free Disk Space' is deprecated.
  Deprecated. Use workflow_settings.free_disk_space instead.
  Free up disk space before build.
  The following components can be cleaned up: apt, cache, docker.
  When set to true, only apt and cache are cleaned up.
  Set it to the full list to clean up all components.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27917746977. Examine the logs at this URL for more detail.}

[traversaro]

I think we can clenaup the conda-forge.yml later, this PR has waited for a bit too long (thanks @oursland for the ping).

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!