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

Loosen Bunny dependency to minor version #372

Merged
merged 1 commit into from
Dec 6, 2018

Conversation

olivierlacan
Copy link
Contributor

Sneakers is currently locking us into a version of Bunny we don't want to be using because the version dependency is tied to the patch-level. Is there a reason for that?

Currently we're locking people into patch versions of Bunny when the project clearly seems to be using SemVer and shouldn't have API breaking changes in minor versions. So this change should make sense.

See: https://github.com/ruby-amqp/bunny/blob/master/ChangeLog.md

Otherwise we're locking people into patch versions of Bunny when they
clearly use SemVer and shouldn't have API breaking changes in minor
versions.

See: https://github.com/ruby-amqp/bunny/blob/master/ChangeLog.md
@olivierlacan olivierlacan mentioned this pull request Oct 18, 2018
@olivierlacan
Copy link
Contributor Author

@michaelklishin could you review and/or merge this? Merging it would allow people to benefit from the queue declaration timeout fix in Bunny 2.12.

See:

Thanks 🤗

Copy link
Collaborator

@gabrieljoelc gabrieljoelc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm good with this. @michaelklishin see any issues?

@lucaong
Copy link
Contributor

lucaong commented Nov 30, 2018

Any update on this? It would be really good to be able to use the most recent version of Bunny

@gabrieljoelc gabrieljoelc merged commit 99f3dc1 into jondot:master Dec 6, 2018
@olivierlacan
Copy link
Contributor Author

@gabrieljoelc Any way I can help you cut a release for this?

@lucaong
Copy link
Contributor

lucaong commented Dec 7, 2018

I would also be happy to help, if anything is blocking the creation of a new release including this change.

@gabrieljoelc
Copy link
Collaborator

@olivierlacan @lucaong thanks for the offer! i started going through the commits that are different between the last release and master but didn't have time to finish and build a changelog entry.

If you are able to help with this, that'd be great. Can you go through those commits and create a PR for the changelog for the new release? If you are able to, can you add any necessary updates to the readme as well please?

Looks like we are behind on release tags/"releases" and published gem versions for 2.8.0 and 2.10.0. If you guys can focus on the changelog and start discussion about the semver number the next release can be, I can try to backfill the other two versions this weekend.

Thanks again for your generous offers!

@lucaong
Copy link
Contributor

lucaong commented Dec 9, 2018

@gabrieljoelc and @olivierlacan, I just compiled a list of changes for the changelog and sent a PR: #378

Feel free to comment on it and let me know if anything is missing

@gabrieljoelc
Copy link
Collaborator

I believe this was the much wanted feature for the the v2.11.0 release, so cc'ing #378 (comment) here as well.

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

Successfully merging this pull request may close these issues.

3 participants