Maintainer Documentation

• Infrastructure
  • Repositories
    • Staging area for recipes
    • Smithy
    • Web services
    • conda-forge pinning
    • Documentation
  • Admin web services
    • @conda-forge-admin, please rerender
    • @conda-forge-admin, please add noarch: python
    • @conda-forge-admin, please update for conda-build 3
    • @conda-forge-admin, please lint
    • @conda-forge-admin, please update team
    • @conda-forge-admin, please restart ci
    • @conda-forge-admin, please ping team
    • @conda-forge-admin, please ping conda-forge/<team>
    • @conda-forge-admin, please rerun bot
    • @conda-forge-admin, please add bot automerge
    • @conda-forge-admin, please remove bot automerge
    • @conda-forge-admin, please add user @username
    • @conda-forge-admin, update version
  • CI build services
    • Azure Pipelines
      • Restarting builds
      • Using Azure for everything
    • TravisCI (IBM Power 8+, ARM)
      • Enabling Travis
    • GitHub Actions
      • Automerge
      • Rerendering
    • Skipping CI builds
    • Third-party Use of Our CI Services
  • Compilers and Runtimes
    • CentOS sysroot for linux-* Platforms
  • Output Validation and Feedstock Tokens
• Contributing packages
  • The staging process
    • Generating the recipe
    • Step-by-step Instructions
      • Checklist
    • Feedback and revision
    • Post staging process
    • Feedstock repository structure
      • recipe
      • LICENSE.txt
      • CI-files
      • conda-forge.yml
    • Maintainer role
    • Adding multiple packages at once
    • Synchronizing fork for future use
  • The recipe meta.yaml
    • Source
      • Build from tarballs, not repos
      • Populating the hash field
      • Downloading extra sources and data files
    • Build
      • Skipping builds
      • Optional: bld.bat and/or build.sh
      • Use pip
    • Requirements
      • Build, host and run
      • Avoid external dependencies
      • Pinning
      • Constraining packages at runtime
        • Defining non-dependency restrictions
        • Defining conflicts
    • Test
      • Simple existence tests
      • Testing python packages
        • Testing importing
        • pip check
      • Running unit tests
        • Test requirements
        • Copying test files
        • Built-in tests
        • pytest tests
      • Command Line Utilities
      • Tests outside of the package
      • Running tests locally for staged recipes
    • About
      • Packaging the license manually
      • SPDX Identifiers and Expressions
      • Licenses of included dependencies
    • Extra
      • Recipe Maintainer
      • Feedstock name
  • Miscellaneous
    • Activate scripts
    • Jinja templating
• Maintaining packages
  • Important notes
    • Packages on conda-forge are immutable
    • Forking and pull requests
      • Pushing to regro-cf-autotick-bot branch
        • How does regro-cf-autotick-bot create automatic version updates?
      • Example workflow for updating a package
  • Updating recipes
  • Rerendering feedstocks
    • Rerendering with conda-smithy locally
    • When to rerender
  • Updating for newly released Python version
  • Testing changes locally
  • Downloading prebuilt packages from CI
  • Removing broken packages
  • Archiving feedstocks
  • Updating the maintainer list
  • Maintaining several versions
• Pinned dependencies
  • Globally pinned packages
  • Specifying run_exports
  • Updating package pins
• Configuring conda-forge.yml
  • Top-level fields
    • appveyor
    • azure
    • bot
    • build_platform
    • build_with_mambabuild
    • channel_priority
    • channels
    • choco
    • circle
    • conda_build
    • conda_forge_output_validation
    • docker
    • github
    • idle_timeout_minutes
    • linux
    • linux_aarch64
    • linux_ppc64le
    • noarch_platforms
    • os_version
    • osx
    • provider
    • recipe_dir
    • remote_ci_setup
    • shellcheck
    • skip_render
    • templates
    • test_on_native_only
    • test
    • travis
    • upload_on_branch
    • win
• Knowledge Base
  • Using CMake
    • Moving from an autotools build to a CMake build
  • Particularities on Windows
    • Local testing
    • Simple CMake-Based bld.bat
    • Building for different VC versions
    • Using vs2019
    • Tips & tricks for CMD/Batch syntax
  • Special Dependencies and Packages
    • Compilers
    • Cross-compilation
    • Rust Nightly
    • Core Dependency Tree Packages (CDTs)
      • libGL
    • Building Against NumPy
    • JupyterLab Extensions
    • Message passing interface (MPI)
      • MPI Variants in conda-forge
      • Building MPI variants
      • Including a no-mpi build
      • Preferring a provider (usually nompi)
      • Complete example
      • Just mpi example
      • MPI Compiler Packages
    • OpenMP
      • Switching OpenMP implementation
    • yum_requirements.txt
    • BLAS
      • Switching BLAS implementation
      • How it works
    • Matplotlib
    • pybind11 ABI Constraints
    • Empty Python packages
    • Non-version-specific Python packages
  • Noarch builds
    • Noarch python
    • Noarch generic
  • Build matrices
  • Requiring newer macOS SDKs
    • Newer C++ features with old SDK
  • PyPy builds
  • Using setuptools_scm
  • Using CentOS 7
  • CUDA builds
    • Testing the packages
    • Common problems and known issues
      • nvcuda.dll cannot be found on Windows
      • My feedstock is not building old CUDA versions anymore
    • Adding support for a new CUDA version
  • Apple Silicon builds
  • Pre-release builds
    • Creating a pre-release build
    • Installing a pre-release build
      • Using the conda CLI
      • Using environment.yml
    • Pre-release version sorting
  • How to update your feedstock token?
  • Using arch_rebuild.txt
  • Migrators and Migrations
  • Security considerations for conda-forge builds
  • Significant Changes To Upstream Projects
    • Python
• FAQ