Closed gr2m closed 10 years ago
see also discussion at https://github.com/hoodiehq/discussion/issues/46
for any Hoodie Module release, update my-first-hoodie dependencies
not necessary, because semver
This is done as per https://github.com/hoodiehq/discussion/issues/46#issuecomment-49161956 The setup is well documented, so once the blocking issues are solved this can come back on the agenda without blocking things on the roadmap.
@boennemann Maybe I misunderstand something, but I think that is not true.
Use case:
0.9.7
to 0.9.8
hoodie new mynewapp
0.9.7
The same is true for
The problem is that hoodie new myappname
only requires the latest hoodie-server
, while the ones listed below are dependencies of hoodie-server
(hoodie-plugins-api
is a dependency of hoodie-plugins-manager
).
I'm not sure if sub-dependencies are covered by semver as well, just want to make sure.
Besides that, what is the workflow if I don't publish a patch version, but a minor / major update?
If you update hoodie.js from 0.9.7
to 0.9.8
you will get 0.9.8
the next time you run hoodie new
(at least with a clean cache, but that's not even needed with https://github.com/hoodiehq/hoodie-cli/issues/121 anymore. Integration tests always run with empty cache).
All my-first-hoodie
dependencies are >1.0
so all non breaking changes will be delivered to new apps immediately (which is kind of what we want).
The only "problem" then would be hoodie-server
dependencies <1.0 (hoodie.js, hoodie-plugins-manager), so here you need to update manually for new feature releases.
Okay, so everytime I publish a new hoodie.js version, I need to manually update hoodie-server and publish it as well, right? Just want to make sure I understand that correctly, thanks!
my-first-hoodie
dependencies