# Patterns for Major Dependency Upgrades

DevFeed: [Patterns for Major Dependency Upgrades](<https://devfeed.tech/articles/the-art-of-a-dependency-upgrade-29352.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/art-of-a-dependency-upgrade/>)

Author: Artur Dryomov

Published: 2018-03-18T00:00:00Z

Content type: article

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [upgrade](<https://devfeed.tech/topics/upgrade.md>), [RxJava](<https://devfeed.tech/topics/rxjava.md>), [Development](<https://devfeed.tech/topics/development.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [dependencies](<https://devfeed.tech/tags/dependencies.md>), [development-process](<https://devfeed.tech/tags/development-process.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [rxjava](<https://devfeed.tech/tags/rxjava.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

## AI overview

The article discusses patterns for major dependency upgrades, using RxJava's transition and EOL as a central example. It explains that major upgrades can drastically change APIs, break code, consume substantial time, affect development processes, and require careful consideration of benefits and migration costs.

## Source excerpt

RxJava 1.x reaches EOL on March 31, 2018, meaning no further development. That's not surprising since the 1.x was in a bugfix-only mode since June 1, 2017. This is an interesting event in a software lifetime, since not so many libraries actually live and prosper long enough to produce a superior version, at the same time handling support for an older version for so long. Fortunately enough, RxJava is one of these lucky projects with maintainers actually caring about users. Thank you, RxJava maintainers, you are real human beings and real heroes.