Maintainer Documentation¶
- Infrastructure
- Repositories
- Admin web services
- @conda-forge-admin, please rerender
- @conda-forge-admin, please add noarch: python
- @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, please update version
- CI build services
- Compilers and Runtimes
- Output Validation and Feedstock Tokens
- Contributing packages
- Maintaining packages
- Pinned dependencies
- Configuring conda-forge.yml
- Top-level fields
- appveyor
- azure
- bot
- build_platform
- build_with_mambabuild
- channel_priority
- channels
- choco
- circle
- conda_build
- conda_build_tool
- conda_forge_output_validation
- conda_install_tool
- conda_solver
- docker
- github
- github_actions
- 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
- Top-level fields
- Knowledge Base
- Using CMake
- Particularities on Windows
- Special Dependencies and Packages
- Noarch builds
- Build matrices
- Requiring newer macOS SDKs
- PyPy builds
- Using setuptools_scm
- Using CentOS 7
- CUDA builds
- Apple Silicon builds
- Pre-release builds
- How to update your feedstock token?
- Using
arch_rebuild.txt
- Migrators and Migrations
- Security considerations for conda-forge builds
- Significant Changes To Upstream Projects
- FAQ