-
Notifications
You must be signed in to change notification settings - Fork 137
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
Addressable dependency #247
Conversation
4f2c8cf
to
fc76a69
Compare
Should |
fc76a69
to
a233e1d
Compare
That is funny. I was wondering how the CI passed, and so did ours after upgrading the gem. It only failed once we pushed it to a prod-like environment... but we use |
😅 thanks for catching it @rally25rs really appreciate it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it should work. Thanks for the super fast turnaround! 👍 Once a new gem version is published I'll give it a test in the same project & environment where we found the issue.
a233e1d
to
b94299e
Compare
I moved it completely into gemspec. I will aim to cut a release for 4.17.1 here within the hour |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changes
Addressable dependency was only avail in development environments through webmock. It should be included in the Gemfile