Update gem version to 0.11.0

[RGBD]

Solves #376. @mknapik you've been pretty active recently in merging pull requests.
Maybe you know what else needs to be done before new gem version release?

[RGBD]

Seems like I'll also have to update pronto-rubocop version to make it work, or update to 0.10.1 but I don't know if master contains breaking changes at the moment.
@mmozuras, @doomspork, @aergonaut , who can I discuss that with?

[doomspork]

Howdy @RGBD I am going to start working through these releases this week. Thanks for helping with this. 👍

I do not believe Master has any breaking changes

[RGBD]

Thanks for the feedback
@doomspork , does it mean we should update to 0.10.1 instead, so that pronto-rubocop is still compatible with the new pronto gem version?

[ashkulz]

Would appreciate if you update CHANGELOG.md here itself, @RGBD 🙂

I think we've had enough new features since 0.10.0 to call it 0.11.0 -- we can always make a new release for pronto-rubocop, but I'm not sure if @doomspork has access to release that gem?

[RGBD]

@ashkulz, alas I don't watch this repo history closely enough to know about all the features, so I've mentioned only the one imortant for me (GitLab MR reviews).
Should I add to changelog every major merge request that happened since last mentioned in the changelog currently (feature #331, bug fix #329)?

[ashkulz]

Sorry for the long delay, but I think yes, that'd be great. I'm still not sure who has access to releasing gems, though.

[RGBD]

Done, @ashkulz.
What's the next step?
Should I also bump pronto-rubocop version?

[ashkulz]

@doomspork?

[smridge]

To get master to work I had to run brew install cmake pkg-config for the rugged dependency. Perhaps this would be good to mention in the README. This will also break CI builds that use pronto.

[ashkulz]

@smridge I think that's been a requirement for quite a while, even 0.10.0 depended on rugged.

[smridge]

@smridge I think that's been a requirement for quite a while, even 0.10.0 depended on rugged.

Ahh ok. Tried it out on a new repo, so that makes sense why I’m seeing all the fun.

[RGBD]

@doomspork, is there any approximate date when this could be reviewed/merged?

[ashkulz]

I've been granted permissions to publish to RubyGems by @doomspork, so I'll try working towards a release by the weekend (unless he has any feedback, of course 🙂).

[doomspork]

Howdy @RGBD and @ashkulz 👋 My apologizes, this was lost in my ever growing notification list 😰

I think 0.11 seems like a sufficient bump. I don't see any reason to consider this a major or patch.

[doomspork]

Something to add to this (given this particular PR), I think we should investigate some of the semantic versioning tools that will handle publishing gems for us as features as added. The biggest change we'll need to make is ensuring PRs update the version accordingly (when necessary) and the changelog.

Automating the release of these packages would greatly reduce the maintenance burden across so many different projects.

https://github.com/semantic-release/semantic-release

[ashkulz]

Thanks for the contribution, @RGBD! I went through the git log and added a few other PRs to the changelog, but added you as a co-author in the above commit 🙂