Can you please tag a new release? #88
Comments
|
I'd rather not tag a release til we're 100% certain we can release it. You can pin it to a commit sha in your Gemfile if you want to be safe. https://bundler.io/guides/git.html
|
katzj
added a commit
to librariesio/libraries.io
that referenced
this issue
Feb 7, 2020
omniauth-github hasn't released a fix yet so pin to a specific rev per their recommendation in omniauth/omniauth-github#88
katzj
added a commit
to librariesio/libraries.io
that referenced
this issue
Feb 7, 2020
omniauth-github hasn't released a fix yet so pin to a specific rev per their recommendation in omniauth/omniauth-github#88
|
I cannot wait for a gem to be cut for this. I don't want to rely on git SHAs in my Gemfile:) I hope we will get a new version soon! Thanks for the work here, I really appreciate how quickly this has been fixed :) |
|
Published 1.4.0 |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given the issues with getting access to Rubygems, we're switching to using a git source.
I'd rather not fetch from the
masterbranch, so are you able to tag a new release which includes the changes in #84 ?The text was updated successfully, but these errors were encountered: