Versioning and dependency management
Versioning is crucial for maintaining compatibility and responsibly managing updates. Properly handling dependencies between packages is equally important, as it ensures that your package works seamlessly with other packages in a project.
Versioning is the process of assigning unique identifiers to different versions of our package. It’s a way to communicate to users how much your package has changed since the last release. There are two main approaches to versioning:
- Semantic versioning:
- Major version: Breaking changes
- Minor version: New features
- Patch version: Bug fixes
An example is 1.0.0, 1.1.0, 1.2.0, and so on
- Date-based versioning:
- Uses dates to indicate when a package was released
An example is 2023.01.01.0
While date-based versioning is simpler, semantic versioning is generally preferred, as it provides more meaningful information about a package’s history.
We can easily define the version of our package...
