Upgrading a Component

BOM Doctor can simulate the health of your application if a component were upgraded to a better version. Typically, a better component leads to a better overall score.

You can simulate upgrading just one component, or several. Select Update to Best Version to immediately update to the version most strongly recommended by BOM Doctor. Select Compare All Versions to see a table of other possible upgrades. The Compare All Versions table also calls out which versions have Breaking Changes – that is, changes to the component's inner workings that might require additional developer time to resolve during the upgrade.

After the Upgrade

Once you've simulated an upgrade, a few things will change.

First, you'll probably see that the components dependencies have changed. In the images below, we upgrade jackson-databind from version 2.13.3 to version 2.13.5. Notice that the scores for jackson-core and jackson-annotations also improve.

This makes sense. After all, what BOM Doctor scores is the quality of your dependencies. If a component's score went up, it's because its dependencies are better!

You'll also notice that the solid blue arrow has changed to a shaded blue arrow. That indicates that an upgrade is currently being simulated for that component.

Finally, you'll notice two new buttons in the left pane.

Select View All to see a changelog of all the upgrades made to components. Select Revert All to revert all simulated upgrades.

Taking the Doctor's Advice

Like what you see? Make the doctor's recommended changes in your application to improve its health.

Changing a transitive dependency is typically more difficult and complex than changing a direct dependency. After the Doctor gives you the diagnosis, focus on upgrading your direct dependencies before you try upgrading your transitive dependencies.

Up Next

How the Doctor Scores