Skip to content

Conversation

@aakashmandavilli96
Copy link
Contributor

@aakashmandavilli96 aakashmandavilli96 commented Dec 8, 2025

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.

@conda-forge-admin
Copy link
Contributor

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.

@aakashmandavilli96 aakashmandavilli96 changed the title Re rendered the feedstock locally and updated teh channel target back to main as this is the mainline branch for the release Re rendered the feedstock locally and updated the channel target back to main as this is the mainline branch for the release Dec 8, 2025
@aakashmandavilli96 aakashmandavilli96 marked this pull request as draft December 8, 2025 23:41
@aakashmandavilli96 aakashmandavilli96 force-pushed the main branch 2 times, most recently from 8f96d61 to b425835 Compare December 11, 2025 21:46
…5.10.28.19.56.30

Other tools:
- conda-build 25.9.0
- rattler-build 0.48.1
- rattler-build-conda-compat 1.4.9
@NewtonDer
Copy link

How did we test this PR?

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.

3 participants