Errors in verification step of installed formula during GitHub Actions CI run

[YOU54F]

There was some errors in the verification step when new releases are created.

See #83 (comment)

It's failing in CI, with the same error above.

I've changed to the following steps.

      - name: Verify tap (⚠️ experimental ⚠️)
        run: |
          hub checkout version/v${{ github.event.client_payload.version }}
          brew install --verbose --debug pact-ruby-standalone.rb
          brew audit --strict --online pact-ruby-standalone

I am not sure if installing the formula from the file is correct.

Once it is built, it complains that my gems aren't built correctly.

There is also this audit issue appearing in CI

pact-ruby-standalone:
  * 2: col 3: Description is too long. It should be less than 80 characters. The current length is 94.
  * Stable: version 1.91.0 is redundant with version scanned from URL
  * Libraries were compiled with a flat namespace.
    This can cause linker errors due to name collisions, and
    is often due to a bug in detecting the macOS version.
      /opt/homebrew/Cellar/pact-ruby-standalone/1.91.0/lib/ruby/lib/libyaml-0.2.dylib

These weren't seen before, as the brew pull command has been deprecated for a couple of years.

It might be okay to merge the PR to master, but I'd like to test it out after, I was hoping I could build it locally and check it all works.

[YOU54F]

hmm seeing the same when just using the archive directly from the pact-ruby-standalone repo

https://github.com/pact-foundation/pact-ruby-standalone/releases/tag/v1.92.00

they are there in the downloaded tarball

[YOU54F]

Yep was an issue with the update to the json gem

[YOU54F]

re-opening, as there is still an issue in the verification step of the tap

https://github.com/pact-foundation/homebrew-pact-ruby-standalone/actions/runs/4618323754/jobs/8165632998#step:5:7

however installed the new version and all is fine locally

[YOU54F]

So errors are now being show and I've stopped it failing the build, everything seems to work in a shakedown despite the linked lib error, and its currently being used in several projects so closing