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

Bump PrettyTables to version 1 in package project file and DataFrames #292

Merged
merged 1 commit into from
Apr 23, 2021

Conversation

andreasnoack
Copy link
Member

to version 1 in test project file. This should hopefully supersede #288, #289, #290, and #291. MLJ is now compatible with PrettyTables version 1 so there is a chance that this PR will pick up the latest versions.

@devmotion
Copy link
Member

But if the latest versions are tested, PrettyTables 0.12 would still be untested, it seems?

@andreasnoack
Copy link
Member Author

Fair point. I've restarted the tests in #290. That should test with 0.12 and then we continue with this one afterward.

@andreasnoack
Copy link
Member Author

Following up on the discussion in #294. I've modified this PR to now allow PrettyTables 0.12. We cannot test that version since MLJ skipped it and went directly from 0.11 to 1.0.

@andreasnoack
Copy link
Member Author

I've added 0.12 back since the conclusion in #294 was the 0.12 had been tested on the runs that exclude MLJ testing.

@andreasnoack
Copy link
Member Author

Tests are passing and version 1 of both DataFrames and PrettyTables are being used. Yay! @devmotion could you please verify and merge if you agree? Once this one is in, I guess we should "rebase" #293. Then a new tag shouldn't be far away and we can move on to the next package that needs to be made DataFrames@1 ready.

Copy link
Member

@devmotion devmotion left a comment

Choose a reason for hiding this comment

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

Looks good, thank you for pushing this update!

@devmotion
Copy link
Member

#293 is already included here, isn't it? So it seems we can just release 4.9.0 once this PR is merged.

@andreasnoack
Copy link
Member Author

You are right. I mentioned exactly that in the top post but had forgotten in the meantime.

...we can just release 4.9.0 once this PR is merged.

Is the policy here to bump the minor version with compact changes. IMO it should be safe just to bump the patch version. (Not that it matters too much.)

@andreasnoack andreasnoack merged commit 1b1f9ba into master Apr 23, 2021
@delete-merged-branch delete-merged-branch bot deleted the an/version1 branch April 23, 2021 08:38
@devmotion
Copy link
Member

Is the policy here to bump the minor version with compact changes. IMO it should be safe just to bump the patch version. (Not that it matters too much.)

There's no strict policy but we tend to bump the minor version (IIRC the reasoning is mentioned in ColPrac: compatibility with new versions of the dependencies is a new feature, not a bugfix).

@devmotion
Copy link
Member

I updated the version number and made a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants