Update version to 0.9.2

[shermansiu]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

• Note: will need to be merged AFTER the server for the other 0.8.3 builds are set up.

Closes #14

[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.

[h-vetinari]

Same concern w.r.t. only one version during development as in #5 (and for all other PRs).

Note, you don't necessarily need to rerender after the skip (I personally like avoiding the churn of deleting and then recreating something in the git history, i.e. the respective variant configs in this case); the other jobs can still exist, but will run through in <5min if skipped, which is a manageable waste of CI time.

[h-vetinari]

Note: will need to be merged AFTER the server for the other 0.8.3 builds are set up.

I would recommend doing this in a separate PR. You can combine it with CUDA 12.9 if you prefer, but cleaner would be to get the builds on main back to green first.

[shermansiu]

Sounds good! I created a PR (conda-forge/.cirun#110) to add a CPU runner, which we can use to bring the other builds green!

[shermansiu]

@conda-forge-admin, please rerender

[shermansiu]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

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

[conda-forge-admin]

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

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

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

[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.