The last release on the 7.x branch was a security release in 2022 and the last feature release in 2019.
So you can hardly say the 7.x branch is still supported.
This problem occurs when using a Drupal version older than 10.3.
I noticed the constraints in composer where not correct, so I updated the info_version_requirement in the .info.yml.
However 1.1.1 is still installable on Drupal 10.2 and older. To fix this, downgrade to 1.1.0.
Merged to 1.1.x. Thanks!
jeroent → created an issue.
I contacted patrickscheffer → about this issue.
Merged to 2.1.x Thanks!
Merged 11.x-dev back into the Merge request !4236
I've added a gitlab-ci.yml file.
There are still some phpstan errors, but those don't seem to be related to the Drupal 11 compatibility. So I guess those can be fixed in a follow-up issue.
The tests were failing because the token hooks moved to a hook class.
Tests are now green again.
I fixed the feedback in the MR.
Merged to 8.x-1.x. Thanks!
I created a new branch, that has 5.0.x as target branch:
https://git.drupalcode.org/project/devel_entity_updates/-/merge_requests/6
The new release is working fine here, Thanks!
I made a mistake in my previous comment. @dqd, you are the owner of the MR, can you edit the target branch to 5.0.x?
#3484837-10: Create D11 compatible version → seems unrelated to the Drupal 11 update and can be handled in a separate issue.
Also, I don't think it's necessary to drop Drupal 10 support, so I would also keep that version in the core_version_requirement property and in composer.json.
@heddn,
I can't find any feedback on the MR?
2 weeks have passed and @markdorison, one of the co-maintainers, also agrees.
deekayen, shrop, ms2011 and bdone can add new maintainers:
https://www.drupal.org/project/r4032login/maintainers.json →
Closing this as a duplicate of 📌 Fix the issues reported by phpcs Active
Closing as a duplicate of 🐛 User logout without CSRF token redirect to 404 Active
The patch no longer works since 💬 Custom entity types Active was committed.
jeroent → made their first commit to this issue’s fork.
I also closed ✨ Adds support for translatable fields Closed: duplicate as a duplicate since that is also fixed here. Because of the changes in .routing.yml file, the entity is loaded immediately in the right language, so translated file fields are already handled.
Closing this as a duplicate of 💬 Custom entity types Active since that is also fixed over there.
This is a nice improvement for this module.
I took the patch in #5, created a merge request of it and made a couple of changes.
I also closed 🐛 Check if node is valid Closed: duplicate as a duplicate since we no longer need to check if the entity is a valid entity because this now happens automatically because of this changes in the routing.yml file:
options:
parameters:
entity:
type: entity:{entity_type}
I'm closing this as a duplicate of 💬 Custom entity types Active .
Once that issue is fixed, this check is no longer necessary because of the changes in the routing.yml file.
jeroent → changed the visibility of the branch 3197043-custom-entity-types to hidden.
jeroent → changed the visibility of the branch 3197043-custom-entity-types to active.
All CS are fixed in 📌 Automated Drupal 11 compatibility fixes for download_all_files Needs review .
📌 Automated Drupal 11 compatibility fixes for download_all_files Needs review will drop support for Drupal 8 and 9 so I guess we can close this one.
Tests are green again.
I contacted Dennis Cohn via the contact form on drupal.org about this issue.
Created a MR that fixes D11 compatibility:
https://git.drupalcode.org/project/one_time_login_link_admin/-/merge_req...
Tests are currently failing.
jeroent → made their first commit to this issue’s fork.