Skip to content
This repository has been archived by the owner on Feb 18, 2025. It is now read-only.

Add changesets to ease versioning #4

Open
ukorvl opened this issue Jun 25, 2024 · 0 comments
Open

Add changesets to ease versioning #4

ukorvl opened this issue Jun 25, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@ukorvl
Copy link
Member

ukorvl commented Jun 25, 2024

We use changesets in niljs.
Actually it works quite well and fixes lots of common problems related to versioning npm package.

Typical problems on automated versioning:

  • It is complicated to agree with all developers when to patch version, when to use minor or major.
  • When both people want to upgrade version simultaneously it will be a mess and merge conflicts in package.json
  • Keeping several versions actual at the same time. It means not to just bump version all the time, but have different branches with different versions and update all of them.
  • How to mention in changelog and release all the changes and determine new version basing on all of the changes since past version? There can be minor, patch and major updates.

We can take changesets from niljs as an example and add it here to have clear changelog and stable process of releasing new versions.

@ukorvl ukorvl added the good first issue Good for newcomers label Jun 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant