Version Auto Increment for any changes merged in "main" branch

[imluckyhussain]

Hi,

I’ve noticed some changes have been merged into the “main” branch, but the version number remains unchanged.

When I delete and reinstall the same package with the same version in my project, the changes don’t seem to be reflected.

I’ve even tried clearing the npm cache and reinstalling the package, but the changes still don’t appear.

Could you please suggest adding a feature that automatically increments the version number once changes are merged into the “main” branch? This would ensure that future changes are reflected in the updated version.

Thanks in advance for your attention to this matter.

[tinchox5]

Hi! You’re right. If the version number doesn’t change, npm won’t detect any updates, even if the code on main has changed.

Right now, I push changes to main before publishing a new version. I agree it can be confusing.

If you want the latest updates, feel free to clone the repo and build your own version (#83).

In the future, I plan to improve the release flow, probably with a dev branch and pre-release versions (like -beta.1) on npm.

Thanks for the feedback, it really helps!

[tinchox5]

From now, I will use dev branch to push changes and community PR, leaving untouched the main branch that holds the last stable release.

For users that want to test latest developments, the idea is to automatically generate prerelease versions every time a change is made in dev branch.

Of course, users can clone dev branch and compile the current state as well.

This prereleases will be unstable by nature 😵‍💫

[imluckyhussain]

Thanks for the updates