|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +comments: false |
| 4 | +title: "Conan Center will stop receiving updates for Conan 1.x packages soon" |
| 5 | +meta_title: "Conan Center will stop receiving updates for Conan 1.x packages soon" |
| 6 | +description: "Conan Center will soon stop providing updates for Conan 1.x packages as the platform shifts focus to supporting Conan 2.x." |
| 7 | +keywords: "conan, conan2, conan center" |
| 8 | +--- |
| 9 | + |
| 10 | + |
| 11 | +Conan 2.0 was released in February 2022 after years in development. Since then, thousands of users and teams have |
| 12 | +adopted Conan 2.0, and the Conan Center Index repository has continued to see significant growth. In 2023, we received |
| 13 | +close to 6000 Pull Requests for recipes. |
| 14 | + |
| 15 | +Since the Conan 2.0 release, and to facilitate the upgrade path for our users, we adopted the decision to make recipes |
| 16 | +in Conan Center compatible with both Conan 1.x and Conan 2.0. |
| 17 | + |
| 18 | +Porting all recipes to be Conan 2.0 compatible has been a significant effort - aided by community contributors to which |
| 19 | +we are very grateful. This has placed additional pressure on all resources, including our CI compute capabilities. This |
| 20 | +has also given the team valuable insights into how to improve and streamline the CI and review processes. |
| 21 | + |
| 22 | +On Conan 2 release day - we had published binaries for the top 120 most used recipes. Today, nearly 97% of all recipes |
| 23 | +in Conan Center are compatible with Conan 2. |
| 24 | + |
| 25 | +As time has progressed, today the majority of requests to the Conan Center remote originate from Conan 2 users. |
| 26 | + |
| 27 | +**Today we are announcing that before the end of the year, new recipe updates in Conan Center will only be compatible |
| 28 | +with Conan 2. Please read below to see how this might affect you.** |
| 29 | + |
| 30 | +## For Conan 1.x users |
| 31 | + |
| 32 | +### Users accessing the ``https://center.conan.io`` remote via the Conan client |
| 33 | + |
| 34 | +The Conan Center remote will stop being updated for Conan 1.x users. This means that from this date: |
| 35 | +- **No new recipe revisions** will be published or visible to the Conan 1.x client. |
| 36 | +- **No new versions of libraries** will be published or made available for Conan 1.x. |
| 37 | +- **No new recipes** will be published or visible for Conan 1.x. |
| 38 | +- All **previously available and published recipes** and binaries will continue to be accessible. |
| 39 | +- **No configuration changes** are required. After the stated deadline, the Conan Center remote for Conan 1.x users |
| 40 | +will be frozen at its current state and will not receive any further updates, as detailed above. |
| 41 | +- Under **exceptional circumstances**, updates may be published for security reasons. |
| 42 | + |
| 43 | +### Users maintaining their own fork of the conan-center-index git repository |
| 44 | + |
| 45 | +- There will be a branch that contains the **frozen versions/revisions** on the aforementioned date - details will follow shortly |
| 46 | +- From then on, we will **no longer guarantee that recipes remain compatible with Conan 1.x** in the main (master) branch. |
| 47 | + |
| 48 | +## For Conan 2.x users |
| 49 | + |
| 50 | +From the date of the switch, new recipe updates will be uploaded internally to a new repository. New details will be |
| 51 | +announced soon, the team is working in two possible solutions to facilitate this transition: |
| 52 | +- Requests coming from Conan 2 clients will be able to see the up-to-date revisions, without impacting legacy Conan 1, |
| 53 | +and without requiring any configuration changes for Conan 1 users. |
| 54 | +- A new remote endpoint will be made public |
| 55 | + |
| 56 | +## Contributions in the conan-center-index repository |
| 57 | + |
| 58 | +- Coinciding with the switch, the Conan Center CI service will only validate recipes and publish packages only for Conan 2 |
| 59 | +- It will no longer be a requirement to retain Conan 1.x compatibility - contributors are free to use Conan 2-only |
| 60 | +features where it aligns with the PR goal |
| 61 | +- **We emphatically ask community contributors to not submit pull requests to perform refactorings to remove old logic or |
| 62 | +mass recipe modernizations**. We want to avoid overwhelming our CI resources and the review team - and continue |
| 63 | +prioritizing new features, bug fixes, new versions, new platforms and new recipes. |
| 64 | + - Pull requests with recipe modernizations only and no functional changes or bug fixes will not be prioritized, and |
| 65 | +we may ask the contributor to reopen the PR at a later date. |
| 66 | + - Pull requests that perform recipe modernizations alongside other valid changes (functional or bug fixes) may |
| 67 | +experience delays in reviews if the changesets/diffs make it less obvious what is being changed. |
| 68 | + - As usual, opening a large number of PRs in a short time is hugely discouraged and against our guidelines. |
| 69 | +- The Conan Center CI service will undergo upgrades to rely on Conan 2 features - further changes will be announced in the near future |
| 70 | + |
| 71 | +For questions or feedback, please follow the discussion in [Github](https://github.com/conan-io/conan-center-index/discussions/25461). |
| 72 | + |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | + |
| 77 | + |
0 commit comments