Release 2.6.0

[adrianna-chang-shopify]

Release a new version so that consumers get the IgnoredPatterns => AllowedPatterns config rename.

Draft release here: https://github.com/Shopify/ruby-style-guide/releases/edit/untagged-048380b893a1794a3cfa

[sambostock]

I think we might need to further bump the minimum required Rubocop version for the config to work. #386 bumped the Rubocop version in Gemfile.lock, and added various configs, but those configs won't exist in the older version of Rubocop.

I'm wondering if we can run CI against both locked version of Rubocop, and also against the oldest supported version, so we're sure it's compatible. 🤔

It's also worth nothing that if we do bump the requirement to 1.29, that version of Rubocop drops support for Ruby 2.5, if I recall correctly.

[sambostock]

Yeah, as I suspected CI fails if we run it with the oldest Rubocop version.

So if we want to release one final version before dropping Ruby 2.5 support, we need to revert #386. Otherwise, we need to bump the minimum Rubocop version.

I have opened #389 to add CI checks for this and tentatively bump the minimum Rubocop version.

[sambostock]

We should address the Rubocop version issue before releasing the next version. One way to do this would be to merge #389 first, if we're okay with springing a minimum Ruby version on our consumers.

#389 has been merged, addressing my concerns. This will need a rebase though.

[adrianna-chang-shopify]

Ah, failing to bump the rubocop version in the gemspec was a complete oversight on my part 🤦‍♀️ Thanks for tackling that @sambostock, and for going the extra mile and tightening up the CI pipeline ❤️ That will definitely help with preserving backwards compatibility for future rubocop version bumps.