back to home

conda-forge / conda-forge-pinning-feedstock

A conda-smithy repository for conda-forge-pinning.

72 stars
583 forks
80 issues
Python

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing conda-forge/conda-forge-pinning-feedstock in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/conda-forge/conda-forge-pinning-feedstock)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

About conda-forge-pinning-feedstock =================================== Feedstock license: BSD-3-Clause Home: https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-pinning Package license: BSD-3-Clause Summary: The baseline versions of software for the conda-forge ecosystem Current build status ==================== All platforms: Current release info ==================== | Name | Downloads | Version | Platforms | | --- | --- | --- | --- | | | | | | Installing conda-forge-pinning ============================== Installing from the channel can be achieved by adding to your channels with: Once the channel has been enabled, can be installed with : or with : It is possible to list all of the versions of available on your platform with : or with : Alternatively, may provide more information: About conda-forge ================= conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a *feedstock*. A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively. To manage the continuous integration and simplify feedstock maintenance, conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender . For more information, please check the conda-forge documentation. Terminology =========== **feedstock** - the conda recipe (raw material), supporting scripts and CI configuration. **conda-smithy** - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of *many* feedstocks. **conda-forge** - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions) Updating conda-forge-pinning-feedstock ====================================== If you would like to improve the conda-forge-pinning recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the channel, whereupon the built conda packages will be available for everybody to install and use from the channel. Note that all branches in the conda-forge/conda-forge-pinning-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks, and branches in the main repository should only be used to build distinct package versions. In order to produce a uniquely identifiable distribution: • If the version of a package **is not** being increased, please add or increase the build/number . • If the version of a package **is** being increased, please remember to return the build/number back to 0. Feedstock Maintainers ===================== • @conda-forge/Core