Release new gem version

[panjan]

Hi,

First of all, thanks for the great gem! ❤️

The last version was released more than a year ago. Are there any plans for the next release?

[aergonaut]

cc @prontolabs/core

[kubamahnert]

Simply tagging the version in git would also suffice. This way, when we want to use newer code than the one released in 0.9.5, we have to reference your commit hashes directly. That's not really pretty..

[dinhhuydh]

goodcheck requires rainbow 3.0 however the Pronto version 0.9.5 limits rainbow at 2.1. The latest master has changed the dependency to >=2.2 which is compatible for goodcheck. Hope that we have next release soon.

[siebertm]

we're running into the same issue as @dinhhuydh, also aergonaut/pronto-goodcheck#1

Our solution for now is to use the master directly in our Gemfile. Not ideal but "works"

[dinhhuydh]

@siebertm Same here.

[williampollet]

Same issue here, react_on_rails depends on rainbow 3.0.

[djpate]

👍 is the project dead?

[doomspork]

@djpate there are commits from just a few days ago, no the project is not dead, that's a foolish thing to ask without even evaluating the project. The project owner, with RubyGem access, has been preoccupied with personal matters. The other maintainers and I on @prontolabs/core have been working very hard to keep things moving.

Please be mindful and considerate of the people who dedicate their free time to making these tools. We are all humans at the end of the day and things do unfortunately come up that have to take priority over open source.

At some point I hope @mmozuras is able to push a new gem and furthermore, give the members of @prontolabs/core access so we can avoid these issues in the future. Until then please use master 👌

[mmozuras]

I've just pushed a new gem version - v0.10.0.

I haven't been a good steward of this project for the last year. Over this month I'll try to consider options on how to make it better. Thanks everyone for your patience! 🙇

[siebertm]

Thanks @mmozuras!

Over this month I'll try to consider options on how to make it better

If this'd be a issue on the tracker, would you mind mentioning me? We're relying on pronto in our core workflows, so we'd like to be on top of things here, no matter what the outcome!