Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

I want to keep landing more breaking changes for Bundler 4.

What is your fix for the problem, implemented in this PR?

  • Completely remove the --rubocop flag to bundle gem, like we've done for other CLI flags.
  • Start ignoring the rubocop setting.

Make sure the following tasks are checked

In Bundler 4, configuration will no longer be updated.
If the CLI flags are used, we abort early as usual.

As per the settings, I decided to ignore them. We've been migrating them
automatically to the new name for a long time and we don't yet have a
standard way to deprecate and remove settings (we should probably use
the existing setting validators). So I think it's fine for now to do
what we normally do (ignore the setting).
@simi simi enabled auto-merge September 12, 2025 11:52
@simi simi merged commit 21533ea into master Sep 12, 2025
76 checks passed
@simi simi deleted the deivid-rodriguez/remove-rubocop-flag branch September 12, 2025 13:22
@deivid-rodriguez deivid-rodriguez mentioned this pull request Sep 12, 2025
21 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants