Skip to content

fix: sagemaker-python-sdk 3.25.0 — region-set import test, fix EOF newline - #377

Merged
aviruthen merged 2 commits into
conda-forge:mainfrom
aviruthen:v3.25.0-noregion-lint-fix
Oct 15, 2026
Merged

aviruthen merged 2 commits into
conda-forge:mainfrom
aviruthen:v3.25.0-noregion-lint-fix

Conversation

@aviruthen

Copy link
Copy Markdown
Contributor

Update to 3.25.0 and fix the two conda-forge CI failures:

  • The import test reached AIRHub (via sagemaker.serve/.mlops), which builds boto3 clients at import time -> NoRegionError. meta.yaml import tests have no env hook, so run them as test.commands with AWS_DEFAULT_REGION set. Upstream source fix tracked in aws/sagemaker-python-sdk PR #6401.
  • Remove the extra trailing blank line flagged by the conda-forge linter. Inter-package floors already match the 1.25.0/2.25.0 wheel requirements.

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

conda-forge-admin commented Oct 14, 2026 •

Copy link
Copy Markdown
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.

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

For recipe/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

    • For the host section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
    • For the run section of the recipe, you should usually use the pin python >={{ python_min }} for the python entry.
    • For the test.requires section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

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

…wline

Update to 3.25.0 and fix the two conda-forge CI failures:
- The import test reached AIRHub (via sagemaker.serve/.mlops), which builds
  boto3 clients at import time -> NoRegionError. meta.yaml import tests have no
  env hook, so run them as test.commands with AWS_DEFAULT_REGION set. Upstream
  source fix tracked in aws/sagemaker-python-sdk PR #6401.
- Remove the extra trailing blank line flagged by the conda-forge linter.
Inter-package floors already match the 1.25.0/2.25.0 wheel requirements.
---
X-AI-Prompt: Fix the conda-forge sagemaker-python-sdk 3.25.0 PR failures (AIRHub NoRegionError on import sagemaker.serve, and the trailing-blank-line linter error) by region-setting the import test as commands and fixing the EOF newline.
X-AI-Tool: Kiro CLI
@aviruthen
aviruthen force-pushed the v3.25.0-noregion-lint-fix branch from 2a7c976 to 9274d16 Compare October 14, 2026 22:55
@aviruthen

Copy link
Copy Markdown
Contributor Author

@conda-forge-admin, please rerender

@aviruthen
aviruthen merged commit ef3d8e0 into conda-forge:main Oct 15, 2026
2 checks passed
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