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

FS6 available installer versions out of sync #9270

Closed
ghost opened this issue Oct 18, 2016 · 5 comments
Closed

FS6 available installer versions out of sync #9270

ghost opened this issue Oct 18, 2016 · 5 comments

Comments

@ghost
Copy link

ghost commented Oct 18, 2016

at

https://github.com/zurb/foundation-sites

FS6 is available via npm installer @ version == 6.2.4rc2

but via bower only at version == 6.2.3

@kball
Copy link
Contributor

kball commented Nov 10, 2016

This has been resolved

@kball kball closed this as completed Nov 10, 2016
@ghost
Copy link
Author

ghost commented Dec 13, 2016

@kball

Once again, now,

FS6 is available via npm installer @ version == 6.3.0.rc2
but via bower only at version == 6.2.4

Is this to be regularly the case? That pkging systems are NOT kept in sync?

Some clarification of simply what to expect would be really helpful.

Different devs use different package mgmt tools; not being able to keep them on the same branch causes problems.

@kball
Copy link
Contributor

kball commented Dec 13, 2016

The rcs should only be available with 'beta' tags, they are not true released versions... so in this case bower is actually correct, I'm not sure why npm is making 6.3.0-rc2 available as a non beta. Looking into it.

@ncoden
Copy link
Contributor

ncoden commented Dec 16, 2016

@user58258 6.3.0 has been released. Is it still an issue ?

@ghost
Copy link
Author

ghost commented Dec 16, 2016

@ncoden

Is it still an issue ?
well, it wasn't after @kball 's last comment ... the published pkg mgr were all in-sync at 6.2.x after what I presume to have been some fix.

& yes, NOW, they're all at 6.3.0, which is great. all devs here are now mindlessly upgrading to the same version of the latest-n-greatest ;-) "Once More unto the Breach!"

We'll see what happens when there's an update ... until I see otherwise, I'm guessing it's been straightened out.

Thanks.

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