-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix deprecations #6
Comments
The commit that adds @benjamintoussaint can you create a new release with this change? Sorry I didn't spot this sooner 🙏 |
The commit `5a797eae17befff34e641f96e04938bd05523eba ` that adds `\Drupal\Core\Utility\Error::logException()` is only present in Drupal `>=10.1`.
@RobinHoutevelts I should have checked that, thanks! |
@RobinHoutevelts Should I maybe add info about deprecations fix in newest tag, prior to delete the previous one? (merge) |
@benjamintoussaint yeah that sounds good. |
We first released `1.3.1` without a fix of Drupal version requirement, fix that we did in `1.3.2`, so now we will delete both `1.3.1` and `1.3.2` and release a new `1.3.1`.
We first released `1.3.1` without a fix of Drupal version requirement, fix that we did in `1.3.2`, so now we will delete both `1.3.1` and `1.3.2` and release a new `1.3.1`.
@RobinHoutevelts You're right! I'm guessing I'll need you to remove tags from GitHub: I was able to delete them on Packagist though. |
@benjamintoussaint I think you have to delete the associated releases first and then you can delete the tags. |
@RobinHoutevelts You were right, thanks 🙏 |
The drupal/upgrade_status module found some warnings.
Not all of them are important. But in this case there is also a found deprecation so I've created this issue.
Scan
The text was updated successfully, but these errors were encountered: