Drop Ruby 2.7 support

[MuriloDalRi]

Ruby 2.7 reaches EOL on 31st March 2023.

#55 should be merged before this.

https://trello.com/c/ynkZlvh8/3119-drop-ruby-27-support-from-gems-3

[kevindew]

@MuriloDalRi you'll also need to change the .ruby-version file to be Ruby 3 as that should match the minimum Ruby version used - which should be 3.0.5

https://docs.publishing.service.gov.uk/manual/publishing-a-ruby-gem.html#ruby-version-compatibility

[MuriloDalRi]

@MuriloDalRi you'll also need to change the .ruby-version file to be Ruby 3 as that should match the minimum Ruby version used - which should be 3.0.5

https://docs.publishing.service.gov.uk/manual/publishing-a-ruby-gem.html#ruby-version-compatibility

I'll update all the PRs.

[kevindew]

@MuriloDalRi you'll also need to change the .ruby-version file to be Ruby 3 as that should match the minimum Ruby version used - which should be 3.0.5
https://docs.publishing.service.gov.uk/manual/publishing-a-ruby-gem.html#ruby-version-compatibility

I'll update all the PRs.

Great, I've realised a couple of other things you'll need to do too:

• Increment the required ruby version in Gemspecs: https://github.com/alphagov/govuk_publishing_components/blob/0d79f88a83abdc34645e1aadf1c128f7b9b9f446/govuk_publishing_components.gemspec#L15 (this project doesn't have one set, which is an indication that we've forgotten to add rubocop to this gem)
• Add an entry to the changelog to say Ruby 2.7 is no longer supported.

[kevindew]

@MuriloDalRi I've opened #55 to add the missing rubocop_govuk dependency, hopefully we can merge that and rebase this.

[MuriloDalRi]

Thanks! I'll add a comment to the PR description.

I think I've made all the changes needed on all PRs now. I'll ask my team for reviews but if you want to have a go, please do!

[kevindew]

Thanks! I'll add a comment to the PR description.

I think I've made all the changes needed on all PRs now. I'll ask my team for reviews but if you want to have a go, please do!

Yup I can review the ones publishing own. It's better if they are reviewed by teams that own the gems, rather than the change just done by your team so that teams are empowered owners and not surprised by changes (even if they're not divisive).

[MuriloDalRi]

That's a good point. The plan was for us to merge these PRs and then raise version bump PRs for teams to review and merge themselves, but I'm happy to let them take it from here.

[kevindew]

That's a good point. The plan was for us to merge these PRs and then raise version bump PRs for teams to review and merge themselves, but I'm happy to let them take it from here.

Sure, I'd not worry about doing version bumps. It doesn't seem necessary to release the dropping of Ruby 2.7 unless there are other changes, so I'd imagine it's best that the Ruby version change just goes out with whatever the next release is.