Conan 3 delivers a refreshed runtime, tighter security boundaries, and modern tooling for developers building cloud native applications. This release aligns with broader industry moves toward more declarative workflows and reproducible deployments at scale.
Engineers can expect clearer upgrade paths, improved observability, and stronger integration with contemporary CI/CD ecosystems. The following sections outline the most impactful changes, configuration options, and operational patterns introduced in this release.
| Release Channel | Version | Release Date | Support Status | Notable Enhancements |
|---|---|---|---|---|
| Stable | 3.0.5 | 2024-03-15 | Production Recommended | Security patches, runtime stability, refined RBAC |
| Preview | 3.1.0-rc.1 | 2024-06-01 | Early Adopter | New scheduler, encrypted artifact transport, enhanced metrics |
| Nightly | 3.2.0-alpha | 2024-07-10 | Evaluation Only | Experimental APIs, WASM extensions, improved tracing |
| Long Term Support | 2.8.4 | 2023-11-20 | Maintenance Mode | Backported fixes, limited feature updates |
Enhanced Runtime Architecture
Isolation and Security Improvements
Conan 3 introduces a hardened runtime that reduces the attack surface for supply chain operations. Process boundaries are stricter, and optional sandboxing is enabled by default for critical workflows.
Performance and Scalability
Parallel downloads, smarter caching, and reduced memory overhead allow teams to handle large monorepos with minimal latency. Benchmarks show noticeable speedups for composite builds and multi-module pipelines.
Configuration and Policy Management
Declarative Settings
New configuration profiles let you define defaults for compilers, architectures, and repository behavior in a single source of truth. Teams can lock down allowed settings and prevent drift across environments.
Policy as Code
Integrated policy evaluation enables automatic rejections of noncompliant artifacts. Fine grained rules can be expressed in standard formats and applied consistently across all pipelines.
Developer Experience and Tooling
CLI Modernization
Cleaner output formats, colored logs, and intuitive error messages simplify debugging. Command autocomplete and improved help text lower the barrier for new contributors.
IDE and CI Integration
First class support for popular IDEs and native steps for major CI platforms reduces setup friction. Generated environment scripts ensure builds are reproducible across machines.
Migration and Upgrade Path
Backward Compatibility Notes
Most existing recipes and ConanCenter packages continue to work, though certain deprecated APIs require updates. The built in migration assistant guides users through required changes step by step.
Testing Strategies
Organizations can run parallel instances of Conan 2 and Conan 3 during a phased rollout. Comprehensive test suites and integration checklists help validate critical workflows before full adoption.
FAQ
How do I upgrade from Conan 2 to Conan 3 without breaking my pipelines?
Run the built in migration assistant in a staging environment, review deprecation warnings, update your recipes to use the new default scopes, and validate with your test suite before promoting to production.
Are packages created in Conan 3 compatible with Conan 2 clients?
Artifacts built with Conan 3 remain compatible when you keep the selected LTS profile and avoid preview only features. For mixed environments, use the compatibility flags and repository proxies provided by the new release.
What new security features does Conan 3 introduce?
Signed provenance attestations, encrypted transport by default, and runtime sandboxing for remote helpers raise the bar for supply chain integrity. You can opt in to stricter verification levels per repository.
What are the hardware requirements for running Conan 3 at scale?
Minimal specifications match contemporary CI runners, while heavy parallel usage benefits from additional CPU cores and fast local storage. Refer to the official sizing guide for large scale index deployments.
Operational Best Practices and Recommendations
- Run the migration assistant in a nonproduction environment first to identify deprecated APIs.
- Adopt declarative settings and policy as code to enforce consistent behavior across teams.
- Enable sandboxing and attestation for regulated workloads to strengthen supply chain security.
- Monitor performance metrics during rollout and adjust parallelism settings for optimal throughput.
- Leverage enhanced logging and structured output to simplify troubleshooting and audit trails.
