what do the numbers mean?

You're getting alerts to upgrade the versions of some of your software dependencies, but you don't want to break anything. Yikes!

By checking the semantic version numbers, you can (fairly) easily decide if you can just merge and deploy or if you need some more thorough testing to see what broke.

is 16.13.0 => 16.13.1 a breaking change?

no.

the final digit is a patch version, and incrementing it means a bug fix with no breaking changes.

Example: https://github.com/facebook/react/releases/tag/v16.13.1

Is 1.19.10 => 1.21.0 a breaking change?

no.

the middle digit is a minor version, so some new stuff was added, but nothing that currently works should break.

Example: https://github.com/kubernetes/kubernetes/releases/tag/v1.21.0

Is 1.49.0 => 1.50.0 a breaking change?

no.

the middle digit is a minor version, so some new stuff was added, but nothing that currently works should break.

Example: https://github.com/rust-lang/rust/releases/tag/1.51.0

Is 15.7.0 => 16.0.0 a breaking change?

yes.

the first digit is a major version, so we definitely expects things that work in 15.7.0 to NOT work in 16.0.0.

Example: https://github.com/facebook/react/blob/master/CHANGELOG.md#breaking-changes

Is 3.9.8 => 3.9.9 a breaking change?

no.

the final digit is a patch version, and incrementing it means a bug fix with no breaking changes.

Example: https://github.com/microsoft/TypeScript/releases/tag/v3.9.9