Cut a new gem release

[markokajzer]

It seems like recently a new version of foundation_emails was released. The release was pushed to npm (2.3.1), but it seems like the gem was not updated (still on 2.2.1.0).

Thanks for the awesome project! Emails are horrible 😄

[golmansax]

Any update on this? Should we use the git repo in the meantime?

[DanielRuf]

@joeworkman

[OleksandrPoltavets]

+1

[Myrronth]

+1

[smserino]

+1

[heycassidy]

+1

[matthewlein]

Is this right? The latest gem uses a 5 years old version, and references possible outdated documentation?

[maxhoffmann]

With the release of Rails 7 using dartsass-rails is now officially recommended instead of using webpacker or sprockets to bundle Sass. Therefore updating the gem to the latest version would be highly appreciated, since upgrading to Rails’ new asset pipeline now means downgrading to an older version of this library

[maxhoffmann]

FYI: adding the latest version via bundler’s Gemfile worked for me

inside Gemfile:

git 'https://github.com/foundation/foundation-emails', tag: 'v2.4.0' do
  gem "foundation_emails", "~> 2.4"
end

then run bundle install

[joeworkman]

I just thought that I should comment here and let you know why this has not happened yet. Sadly, I do not have the rights to publish this to ruby gems at this time. I have email the person that does own the account and have also contacted ruby gems support for help.

Thanks to @maxhoffmann for the tip!

[TikiTDO]

@joeworkman If you're having trouble getting access to the original gem, could you just make a new gem? Something like foundation_emails2 or the like? Pointing at tag in a code repo isn't really the best from a security standpoint. It's much easier to audit, validate, and cache individual libs from an immutable service like rubygems.