lfdebrux
commented
1 year ago This has been fixed now, thanks for raising.
Closed jfharden closed 1 year ago
lfdebrux
commented
1 year ago This has been fixed now, thanks for raising.
What should change
Currently the post-merge publishing workflow is failing since no ruby version is specified for the ruby/setup-ruby github action.
We should either specify ruby 3.2 in the workflow file, or include a .ruby-version (or .tool-versions) file in the project root specifying 3.2.
User need
To get the newest versions of the gem