[wteuber]

Summary

bundle fails on the pinned Ruby 4.0.4 (.ruby-version):

unicode-emoji-4.0.4 requires ruby version >= 2.5, < 4.0, which is incompatible with the current version, 4.0.4

This updates Gemfile.lock only:

• unicode-emoji 4.0.4 → 4.3.0 and unicode-display_width 3.1.4 → 3.3.0 (both require Ruby >= 2.5). Updated with bundle lock --update … --conservative, so json, prism and RuboCop 1.77.0 stay as locked.
• BUNDLED WITH 2.5.22 → 4.0.19, the Bundler that ships with Ruby 4.0. On RubyGems 4.0, Bundler 2.5.22 prints already initialized constant Gem::Platform::… warnings. Under bundle exec they leak into the CLI subprocesses' stderr and fail 7 integration tests that assert empty stderr.

Impact

• No runtime change: the gem has no runtime dependencies, and the gemspec doesn't read the lockfile.
• CI is unaffected: the Ruby 2.6/3.4/4.0 test jobs run without Bundler, and the RuboCop job uses gem install rubocop -v 1.77.0.
• Bundling on Ruby < 3.2 (Bundler 4's floor) was already impossible, since RuboCop 1.77 needs Ruby >= 2.7. Ruby 2.6 support is unchanged: the suite still runs on stdlib only (verified on macOS /usr/bin/ruby 2.6.10: 204 runs, 0 failures, 100% coverage).

Verification (Ruby 4.0.4)

• bundle install resolves and installs.
• bundle exec rake: 204 runs, 0 failures; RuboCop: 32 files, no offenses.