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.

Sign up for GitHub

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

Jump to bottom

Compatibility with Middleman 4.1.7 #122

Open
ryankbales opened this issue Apr 28, 2016 · 4 comments
Open

Compatibility with Middleman 4.1.7 #122

ryankbales opened this issue Apr 28, 2016 · 4 comments

Comments

@ryankbales
Copy link

I recently upgraded to Middleman 4.1.7 from 4.0. Here is the issue in regards to my experience. Short of it is, it looks like there needs to be a gem release if it is ready. Thanks.
@ryankbales ryankbales mentioned this issue Apr 28, 2016
Closed
@nkabardin
Copy link

Any updates here?

@douglascamata
Copy link

Ping! (just 'cause this project and great and does not deserve to die)

@douglascamata
Copy link

BTW, I think this repository needs to be reorganised. If version 2.0.0 is alpha until now because it needs more issues to be solved, maybe we could help if they were tagged.

@MaybeThisIsRu
Copy link

Had to come here for the solution. Ruby community known to be very collaborative, but was disappointed with this. How can we fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@douglascamata @nkabardin @ryankbales @MaybeThisIsRu