Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: how to publish on releases of submodules #39

Open
gr2m opened this issue Dec 26, 2015 · 3 comments
Open

Question: how to publish on releases of submodules #39

gr2m opened this issue Dec 26, 2015 · 3 comments

Comments

@gr2m
Copy link
Member

gr2m commented Dec 26, 2015

I’ve published a new version with a fix: https://github.com/hoodiehq/hoodie-client-store/releases/tag/v3.0.2

When I install Hoodie, I don’t get the fix, because hoodie-client gets build on publish, and it does not get published when a sub library gets released.

Any idea how to handle this?

gr2m added a commit that referenced this issue Dec 26, 2015
* * *

This commit was sponsored by &yet.

Our friends at &yet have been supporters of Hoodie since its earliest days. <3
And they have availability for new projects! We think they’re some of the best
people you can hire anywhere, but you can read what other people have to say
about them and their work here:

https://andyet.com/case-studies/
@gr2m
Copy link
Member Author

gr2m commented Dec 26, 2015

I disabled caching for now, as even when published it didn't have the latest version of hoodie-client-store. I had to delete travis cache & publish again

@varjmes
Copy link

varjmes commented Dec 26, 2015

@gr2m Is there any way to use bundle bump bot to do this? If client-store gets updated, then bundle bump bot prs the updated to hoodie-client?

@gr2m
Copy link
Member Author

gr2m commented Apr 18, 2016

yes bundle bump bot is the right way to do this 👍

I’d suggest we add it to all Hoodie client modules:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants