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

Release a version that does not cause Hashie conflict messages #113

Closed
shawnacscott opened this issue Jan 3, 2022 · 2 comments
Closed

Comments

@shawnacscott
Copy link

Is your feature request related to a problem? Please describe.
The most recently released version of this gem (1.18.0) produces an error with the pinned hashie version, as seen in #41. This has been fixed in #112, but is not yet included in any released version. This has caused a huge amount of log spam that my applications must filter or suppress.

Describe the solution you'd like
A new version release that includes work completed in #112.

Describe alternatives you've considered
Currently, my workaround is to pin this gem's version via ref, like gem 'boxr', github: 'cburnette/boxr', ref: '140f0d'. However, I would prefer to rely on an official version.

Additional context
I would be happy to submit a PR to bump the version to 1.19.0, but did not see any documentation on whether that would meet the requirements for a version release. Please let me know if a PR would be welcome, or if there are other requirements that must be met before boxr can have a new version release.

@xhocquet
Copy link
Collaborator

xhocquet commented Jan 3, 2022

Thanks for the heads up @shawnacscott! I'll cut a release as soon as I can, sorry for the headache

@xhocquet
Copy link
Collaborator

xhocquet commented Jan 5, 2022

@shawnacscott New release 1.19.0 is now available - https://rubygems.org/gems/boxr/versions/1.19.0

@xhocquet xhocquet closed this as completed Jan 5, 2022
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