-
Notifications
You must be signed in to change notification settings - Fork 39
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
Versioning for breaking releases #232
Comments
Hi @itsdfish ! Ouch, I might have removed the deprecated keywords in the wrong branch. I will revert this problem and tag a new version this weekend. Thanks for the report. |
No problem! I completely understand how that can happen. Thank you for fixing the versions. |
Also, it appears that I may have misunderstood the nature of the problem here. If I understand correctly, the deprecation warnings are hidden by default, and fallback on the deprecated method. So it looks like I was unknowingly using the old method, and only noticed the problem once the deprecation warning was removed. I updated my code accordingly. Sorry for the confusion! |
Ok! So let's just issue open and if anyone else complain I will revert the commit. Thanks! |
I had this issue. For anyone else who runs across it, a simple fix is to downgrade to v2.2.7 Here's the relevant error message, which make help Google searches:
|
Hello,
Thank you for this package. I found it to be quite useful for several of my projects. I am opening an issue because there were breaking changes sometime between 2.0 and 2.3.1, specifically in the keyword names used in
pretty_table
. Here is a description of the problem on Discourse. Based on the docs for Pkg.jl, my understanding is that a breaking change should have changed the major version to 3.0. The documentation notes:The text was updated successfully, but these errors were encountered: