Skip to content

[bot-automerge] sagemaker-python-sdk v3.15.0 - #374

Closed
regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:3.15.0_h84ecaf
Closed

regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:3.15.0_h84ecaf

Conversation

@regro-cf-autotick-bot

Copy link
Copy Markdown
Contributor

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.

Closes: #370
Closes: #371
Closes: #372

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: disabled to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by grayskull shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by grayskull but not in the meta.yaml:

  • setuptools >=64
  • pip
  • python {{ python_min }}.*
  • python >={{ python_min }}
  • sagemaker-serve >=1.14.0,<2.0.0
  • sagemaker-core >=2.14.0,<3.0.0
  • sagemaker-train >=1.14.0,<2.0.0
  • sagemaker-mlops >=1.14.0,<2.0.0

Packages found in the meta.yaml but not found by grayskull:

  • sagemaker-train >=1.12.0,<2.0.0
  • sagemaker-mlops >=1.12.0,<2.0.0
  • sagemaker-core >=2.12.0,<3.0.0
  • python >=3.9
  • sagemaker-serve >=1.12.0,<2.0.0

This PR was created by the conda-forge-bot. The conda-forge-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/conda-forge/conda-forge-bot/actions/runs/28281629928 - please use this URL for debugging.

@conda-forge-admin

Copy link
Copy Markdown
Contributor

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

  • ❌ There are 1 too many lines. There should be one empty line at the end of the file.

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

@conda-forge-admin

Copy link
Copy Markdown
Contributor

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

I considered the following status checks when analyzing this PR:

  • linter: failed
  • github-actions: failed

Thus the PR was not passing and not merged.

@aviruthen aviruthen added the bot-rerun Instruct the bot to retry the PR label Oct 14, 2026
@regro-cf-autotick-bot

Copy link
Copy Markdown
Contributor Author

Due to the bot-rerun label I'm closing this PR. I will make another PR as appropriate. You should expect to wait at least a few hours, or possibly much longer, for a new PR.

This message was generated by https://github.com/conda-forge/conda-forge-bot/actions/runs/38645054951 - please use this URL for debugging.

@regro-cf-autotick-bot
regro-cf-autotick-bot deleted the 3.15.0_h84ecaf branch October 14, 2026 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot-rerun Instruct the bot to retry the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants