Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Upgrading dependencies is essential for maintaining security and compatibility. The specific level of effort varies from library to library, but there are several steps that should be followed for all dependency upgrades.

Standard Steps

Projects follow various versioning strategies, which often complicates the upgrade process. Understanding project versioning strategy is important when evaluating changes.

  1. Evaluate project versioning strategy
  2. Review project release notes
  3. Determine level of changes
  4. Review direct dependency references
  5. Review transitive dependency references
  6. Run local build
  7. Run GitHub automated builds in forked repository

Evaluate Project Versioning Strategy

Projects follow various versioning strategies, which often complicates the upgrade process. Understanding project versioning strategy is important when evaluating changes.

Many projects adhere to Semantic Versioning for project releases. Semantic Versioning aims to provide a common approach to version number numbering in a way that communicates the type of changes included. Major versions can include some number of breaking changes, whereas minor and patch versions should never include breaking changes.

...