Pin ruby 3.3.3 instead of 3.3.x during workflow builds
#384
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Address newly build errors stemming from Ruby 3.3.7 not having the proper file permissions during
bundle install:The installation path is insecure. Bundler cannot continue. /opt/hostedtoolcache/Ruby/3.3.7/x64/lib/ruby/gems/3.3.0/gems is world-writable (without sticky bit). Bundler cannot safely replace gems in world-writeable directories due to potential vulnerabilities. Please change the permissions of this directory or choose a different install path.Bumping bundler to
2.5.19should resolve this as well but it makes more sense to pin the ruby version here with what's used innetlify.tomland the rest of thewai-websiteresources (as it should have been from the start)