Josh Powell

poke @seejohnrun ☝🏻

Is this still of interest?

FYI...@lani13 I'm also failing on the same spec here #156

CI fails on all Spree 3.2 which supports Rails 5.0. Green for [Spree >= 3.3](https://github.com/spree/spree/releases/tag/v3.3.0) Perhaps its worth versioning this Gem?

@damianlegawiec @bbonislawski any suggestions/thoughts on how to proceed? Is this something you'll want up to date for the [Rails 5.2](https://github.com/spree/spree/pull/8601) bump? I'll gladly work up a PR. Trying not to...

@stevenharman your suggestion worked for me.

a recent (unreleased) patch in rails may resolve the issue: https://github.com/rails/rails/pull/49621 ```ruby gem "rails", git: "https://github.com/rails/rails.git", branch: "7-1-stable" ```

@jayzes this heroku-buildpack-jemalloc fork accommodates both stack and version. https://github.com/gaffneyc/heroku-buildpack-jemalloc/blob/master/bin/compile heroku-18 was just released https://github.com/gaffneyc/heroku-buildpack-jemalloc/commit/28198d9f7b4db7a86a7b010e1933494803157929 perhaps this buildpack could incorporate some of the progress made there.

Link to Article detailing the end of life/support for MD5 Hash and it's replacement option: [MD5 Hash End of Life & Signature Key Replacement](https://support.authorize.net/s/article/MD5-Hash-End-of-Life-Signature-Key-Replacement?utm_campaign=19Q2+MD5+Hash+EOL+Developer&utm_medium=email&utm_source=Eloqua) Link to [Upgrade Guide](https://developer.authorize.net/support/hash_upgrade/)

Anyone know how this recent change in Rails https://github.com/rails/rails/commit/d0af407ec0187555cba332943b7d89262fc532bc impacts this Gem?