Skip to content

Conversation

@michaelvay
Copy link
Contributor

@michaelvay michaelvay commented Jan 20, 2026

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/meta.yaml) and found it was in an excellent condition.

@michaelvay
Copy link
Contributor Author

Closes #350
The relaxation is already implemented in https://github.com/aws/sagemaker-python-sdk/blob/v2.254.1/pyproject.toml#L48

Currently blocking us from building conda envs with sagemaker-python-sdk and pytorch>=2.8

@michaelvay
Copy link
Contributor Author

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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/21167234861. Examine the logs at this URL for more detail.

@michaelvay
Copy link
Contributor Author

Hi @claytonparnell, again would be glad if you have a moment to review this tiny change, regarding requirement matching with the pip package.

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.

2 participants