Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Ruby 3.0 to CI matrix #171

Merged
merged 8 commits into from
Sep 17, 2021
Merged

add Ruby 3.0 to CI matrix #171

merged 8 commits into from
Sep 17, 2021

Conversation

robbkidd
Copy link
Member

@robbkidd robbkidd commented Sep 14, 2021

Which problem is this PR solving?

  • The absence of testing the latest version of Ruby.

Short description of the changes

  • Easiest to walk the commits, starting with the first. Each commit message describes a discrete fix for adding Ruby 3.0 to the matrix.

... which was removed from stdlib in Ruby 3.0. So bring it back for now.
Enables the legacy Ruby 2 handling of keyword arguments.
The last sequel v4 release was in 2017. If someone is still using that
version, they're not using Ruby 3.
@honeycombio honeycombio deleted a comment from codecov bot Sep 15, 2021
@robbkidd robbkidd marked this pull request as ready for review September 15, 2021 19:31
@robbkidd robbkidd requested a review from a team September 15, 2021 19:31
@robbkidd robbkidd added type: maintenance The necessary chores to keep the dust off. version: no bump A PR with maintenance or doc changes that aren't included in a release. labels Sep 15, 2021
@@ -124,7 +124,7 @@ workflows:
- lint
matrix:
parameters:
ruby-version: ["2.2", "2.3", "2.4", "2.5", "2.6", "2.7"]
ruby-version: ["2.2", "2.3", "2.4", "2.5", "2.6", "2.7", "3.0"]
Copy link
Member Author

@robbkidd robbkidd Sep 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: Ruby 2.2 is included in the test matrix and is the minimum version declared in the gemspec, but the README says Ruby 2.3+ is required. I'm inclined to let it ride for now. I'm sure we'll be dealing with it when we go to move the version constraint on libhoney when the new major version of it releases.

Copy link
Contributor

@vreynolds vreynolds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

onward

@honeycombio honeycombio deleted a comment from codecov bot Sep 16, 2021
@honeycombio honeycombio deleted a comment from codecov bot Sep 17, 2021
The splatting of keywords is handled by the middleware callers.
@honeycombio honeycombio deleted a comment from codecov bot Sep 17, 2021
@robbkidd robbkidd merged commit e3901aa into main Sep 17, 2021
@robbkidd robbkidd deleted the robb.add-ruby-3-to-ci branch September 17, 2021 17:19
@JamieDanielson JamieDanielson added version: bump patch A PR with release-worthy changes and is backwards-compatible. and removed version: no bump A PR with maintenance or doc changes that aren't included in a release. labels Sep 20, 2021
@robbkidd
Copy link
Member Author

Switched back to a patch bump and pending release because of the code changes to client-side integrations. This wasn't only an update to the test suite, so those client-side changes should get released distinctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance The necessary chores to keep the dust off. version: bump patch A PR with release-worthy changes and is backwards-compatible.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants