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

Potential to cut a new release? #129

Closed
itsliamegan opened this issue Jan 20, 2021 · 2 comments
Closed

Potential to cut a new release? #129

itsliamegan opened this issue Jan 20, 2021 · 2 comments

Comments

@itsliamegan
Copy link

Since v0.21 doesn't include #127, using the most recent version from RubyGems still causes the warning described in that issue. Would it be possible to release a new version that includes the fix (and of course the other few fixes since v0.21)?
@gjtorikian
Copy link
Owner

Oh definitely, I hadn't realized that. I'll put out a patch now.

@gjtorikian
Copy link
Owner

Done!

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
2 participants
@gjtorikian @itsliamegan