Check for Breaking Changes Before Upgrading

Upgrading a major dependency without checking the changelog is how production breakages happen. The API may have changed, a method may have been renamed, or a default behaviour may have been altered in a way that only surfaces at runtime. Reading through changelogs and migration guides manually takes time that most engineers skip under deadline pressure.

The resolve_library and get_docs skills fetch current documentation for any package, including changelogs, migration guides, and version-specific API references. You can ask about what changed between two versions, what the migration path looks like, and which parts of your existing code are affected.

Engineers planning major version upgrades, teams maintaining large dependency trees, and tech leads reviewing upgrade risk before a sprint all use this to make informed upgrade decisions without reading through GitHub release pages manually.