-
Notifications
You must be signed in to change notification settings - Fork 76
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
Use version constant directly #985
Conversation
@pfefferle Do you have any guidance on this?
|
@obenland Oh, haven't seen that, sorry! We follow semantic versioning, so fully removing the functions would have required a 5.0.0 release due to the breaking change. Since you retained the functions and added a deprecation warning, opting for the next possible minor version makes total sense. |
Do you have a preference one way or the other? |
Exactly like you've done it: https://github.com/Automattic/wordpress-activitypub/pull/968/files#diff-2fb16a1f775688a0027ff486df52ce4bb27d1c754b878990408219982d3205b4 Keeping the old files/classes/functions for a while, add deprecation message and remove them with the next major version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense!
Since
ACTIVITYPUB_PLUGIN_VERSION
gets defined at the top ofactivitypub.php
,get_plugin_version()
will always return that and never fall back to the plugin meta information.Not sure if 4.2.0 is the right version number in the deprecation documentation.
Not sure even if deprecating function is something this plugin does, or if it breaks back compat.
Proposed changes:
Activitypub\get_plugin_version()
andActivitypub\Migration::get_target_version()
in favor ofACTIVITYPUB_PLUGIN_VERSION
.