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

remove puma from .gemspec #342

Merged
merged 1 commit into from
Apr 13, 2020
Merged

remove puma from .gemspec #342

merged 1 commit into from
Apr 13, 2020

Conversation

jrochkind
Copy link
Contributor

It's not actually a dependency of this gem; apps using this gem do not need puma installed, let alone a specific version of puma.

Past commit message at 0a9ed02 suggested puma was needed here for circle-ci to succeed, but let's see if that's still true.

Could resolve #337

It's not actually a dependency of this gem; apps using this gem do not need puma installed, let alone a specific version of puma.

Past commit message at 0a9ed02 suggested puma was needed here for circle-ci to succeed, but let's see if that's still true.
@jrochkind
Copy link
Contributor Author

Not sure why coverage/coveralls is still stuck in expected/waiting -- that seems to be urnelated, because it's all true in other recent PRs, such as #317? Would it make sense to remove that as a required check, since it's not working?

Other than that, all tests seem to be passing?

This suggests that having puma in the gemspec is not required for circle-ci success, at least not currently? Since the commit message in 0a9ed0 when puma was added to gemspec suggests it was added in order to make circle-ci pass... if it is no longer required for circle-ci to pass, can it simply be removed? And then resolve #337, to to longer put restrictions on what version of puma (if any) a using application is using?

@jrgriffiniii jrgriffiniii merged commit 3ec420a into master Apr 13, 2020
@jrgriffiniii jrgriffiniii deleted the remove_puma branch April 13, 2020 23:05
@jrochkind
Copy link
Contributor Author

Thank you @jrgriffiniii , appreciate it!

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.

browse_everything 1.0.2 improperly locks to puma 3.x
2 participants