# Upgrading from Ray 1.11 to Ray 2.0.0

**URL:** https://discuss.ray.io/t/upgrading-from-ray-1-11-to-ray-2-0-0/7381
**Category:** RLlib
**Created:** [August 30, 2022, 12:20pm UTC](https://discuss.ray.io/t/upgrading-from-ray-1-11-to-ray-2-0-0/7381 "2022-08-30T12:20:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![hridayns](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/hridayns/32/1222_2.png) [@hridayns](https://discuss.ray.io/u/hridayns)
#### Post date: [August 30, 2022, 12:20pm UTC](https://discuss.ray.io/t/upgrading-from-ray-1-11-to-ray-2-0-0/7381/1 "2022-08-30T12:20:41Z")

</div>

**How severe does this issue affect your experience of using Ray?**

- Medium: It contributes to significant difficulty to complete my task, but I can work around it.

Hello,

is there a way to upgrade from Ray 1.11 to Ray 2.0.0. It seems many things have changed, and it’s not entirely clear the exact modification of each component of code that may be causing a certain issue. Is there a way to do this systematically? Some place where I can compare the exact changes that need to take place? For example, (hypothetically) tune.run() has to now be replaced with tune.run\_experiment() and the parameters that have been renamed: …, removed: …, etc.?

---

<div class="post-metadata">

### Author: ![RaymondK](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/raymondk/32/2652_2.png) [@RaymondK](https://discuss.ray.io/u/RaymondK)
#### Post date: [August 31, 2022, 9:20am UTC](https://discuss.ray.io/t/upgrading-from-ray-1-11-to-ray-2-0-0/7381/2 "2022-08-31T09:20:32Z")

</div>

There is the Ray 2.0 migration guide: [Ray 2.0 Migration Guide - Google Docs](https://docs.google.com/document/d/12ODPbhEzeyDRUt8ehHDiKCFoxksPWJOUNEicGhNxtRg/edit#)  
Which can be found on the release notes: [Release Ray-2.0.0 · ray-project/ray · GitHub](https://github.com/ray-project/ray/releases/tag/ray-2.0.0)  
This helped a lot for me.