Jon Roberts

My config above doesn't work anymore, not sure why. I haven't noticed for a while but I'm assuming it happened around either the NixOS 19.09 or 20.03 upgrade.

[OpenSSL 3.0 is now released](https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/) (and is now the default version on [Homebrew](https://github.com/Homebrew/homebrew-core/commit/92d985af3e3757d045d1ce5f0db52ddf1e557108))

Same here, using act v0.2.31 and a known good github token (which is also present in the current env, but figured I'd explicitly pass it into act as well): ```...

:+1: This would be useful. Adding another YAML level is probably the best approach.

I was just looking at using rswag, but maintain a number of projects that only use minitest (and I like it that way...), so this issue is critical for me.

So then is there currently any way to use `elasticsearch-rails` on an app that also has `faraday '~> 2.0'`? It looks like only `elasticsearch-transport '>= 8.1'` supports a modern Faraday...

Try adding this step: ```yaml - name: Install Chrome Deps run: | sudo apt-get update sudo apt-get install -y ca-certificates fonts-liberation libappindicator3-1 libasound2 libatk-bridge2.0-0 \ libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3...

According to https://github.com/browser-actions/setup-chrome#setup-chrome it looks like you can't specify a version yet, only a release channel.

This is a really minor change, but fixes an annoying deprecation warning and works with all currently supported versions of ruby. Could we get this merged soon?

Ping