Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recipe updates for v1.13.0 #54

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

mattkram
Copy link

@mattkram mattkram commented Nov 1, 2024

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.

We've made a few fundamental changes to anaconda-client in v1.13.0. The changes are non-breaking and backwards-compatible.

With this release, we have moved the anaconda entrypoint into anaconda-cli-base, and converted the core binstar.scripts.main entrypoint to be a subcommand plugin. We have implemented backwards-compatible logic to mount all existing subcommands to the parent CLI. For now, if anaconda-client is installed as the only plugin package, the CLI should be identical.

The library interfaces haven't changed.

I wanted to bring this PR manually to draw awareness to the conda-forge team, since I know this is used in automation scripts. I'd also like to offer myself to become a maintainer of this feedstock, if the team is willing. I will be leading the CLI efforts for Anaconda in the future, so I'd love to help streamline the process.

More details can be found in the release notes.

@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.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • No valid build backend found for Python recipe for package anaconda-client using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

@mattkram
Copy link
Author

mattkram commented Nov 1, 2024

@conda-forge-admin, please rerender

conda-forge-webservices[bot] and others added 4 commits November 1, 2024 14:02
I accidentally generated it with a "v" before the version number in the
filename
@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.

@mattkram mattkram mentioned this pull request Nov 2, 2024
3 tasks
@mattkram
Copy link
Author

Hi @jakirkham, @mbargull!

Just wanted to bring this to your attention. We released v1.13.0 to main yesterday.

Also, happy to take over maintenance of this feedstock if you are interested.

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