Geoffrey Hichborn

I've reproduced this in 4.1.6.

I'm seeing an identical issue here, where `most-gems` is including `aws-partitions` instead of the `aws` group. ``` - package-ecosystem: bundler registries: '*' directory: '/' schedule: interval: weekly groups: most-gems: applies-to:...

I believe this is because `most-gems` includes a gem that depends on `aws-partitions`, which causes the exclusion matcher to be shortcutted [here](https://github.com/dependabot/dependabot-core/blob/2bac7735d106b1023a461d567db9d044fd1618f0/common/lib/dependabot/dependency_group.rb#L46) The reporter is seeing this because `yabeda-karafka-2` depends...

This [comment](https://github.com/rubygems/rubygems/pull/2894/commits/9a401646e1725dec471e6b22b4670ebcb3191c0d#diff-f783227fd53e00e4b8e090ab582c1442682b08ea10b280063a1ab4fdcea936efR154) is just incorrect.

What's holding up the ability to change models?

Another member of my team (but not me) is also getting this exact error (same actual and expected hashes). Has a bad copy of the provider been published to some...

I wasn't able to reproduce it myself, but the member of my team running into this was located in India.

FWIW, `def foo = 42 unless defined?(:foo)` and ```ruby def foo 42 end unless defined?(:foo) ``` seem like major anti-patterns.

It's already available for [ElasticBeanstalk on AL2023](https://aws.amazon.com/about-aws/whats-new/2025/02/aws-elastic-beanstalk-ruby-3-4-amazon-linux-2023/), so what's the hold up here? I usually expect ElasticBeanstalk to be trailing in terms of updates rather than leading.