Skip to content

Conversation

@mikeastock
Copy link

No description provided.

@thomaswitt
Copy link

I would appreciate a quick merge. The ruby is outdated since more than half a year.

@icaroryan
Copy link

icaroryan commented Nov 10, 2025

@thomaswitt As a workaround, to remove the ruby requirement version when starting the container, I'm running the following script before installing my gems

# Check Ruby version compatibility
RUBY_VERSION=$(cat .ruby-version | tr -d '[:space:]')
CURRENT_RUBY=$(ruby -v | awk '{print $2}' | cut -d'p' -f1)
echo "Ruby version check: $CURRENT_RUBY (required: $RUBY_VERSION)"

# Removing Ruby version requirement from Gemfile
if [ "$CURRENT_RUBY" != "$REQUIRED_RUBY" ]; then
  echo "Ruby version mismatch — commenting ruby version requirement in Gemfile..."
  # Only comment if the line isn't already commented
  sed -i '' "s/^\s*ruby\s\+['\"][0-9.]\+['\"]/&#/" Gemfile
  # Ignore Gemfile changes for this session
  git update-index --assume-unchanged Gemfile Gemfile.lock
fi

This script will basically go into the Gemfile and comment out the line where we specify the ruby requirement version

This way you can still build your container and install gems without crashing. Chances are all gems from 3.4.4. are compatible to 3.4.7, so it should be fine until this ticket is merged.

@thomaswitt
Copy link

This way you can still build your container and install gems without crashing. Chances are all gems from 3.4.4. are compatible to 3.4.7, so it should be fine until this ticket is merged.

Thanks for the suggestion!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants