Every Meteor release includes a version bump for all core packages (this is also the commit that is tagged as the release itself, AFAICT), regardless if anything actually changes.
This causes new versions to be downloaded for all of the used core packages even if nothing changes.
In case someone (like me) maintains a local fork of some core packages, this leads to 2 issues:
- I have to match the fork version with the released version. This becomes an issue when I have multiple projects with different Meteor versions and the packages are symlinked to a main working directory.
- It makes it more difficult to figure out when something actually changes or this is a “blank” version bump.
I am wondering what is the purpose of this (having a dependency on an explicit package versions, I guess) and whether it is really necessary.
Is there a better alternative to this approach?
Is there a way to maintain a fork to a core package without experiencing this pain?
Do you think it worth a discussion?