Test coverage shows the issue is fixed. Contrib tests in 🐛 Fix tests (next minor) Active are fixed as well with this change. Thanks!
I filed an issue for Drupal Core: 🐛 A reverted revision is not listed on the version history Active
\Drupal\node\Form\NodeRevisionRevertForm does not call \Drupal\Core\Entity\ContentEntityStorageBase::createRevision that sets the revision_translation_affected.
See \Drupal\Core\Entity\Form\RevisionRevertForm::prepareRevision for reference
These test failures now affect the regular 'phpunit' pipeline step
Closed as a duplicate of 🐛 Fix tests (next minor) Active
Patch file for 8.x-1.x for projects running the final version of 8.x-1.x
The merge request removes the outdated \Drupal\Tests\diff\Functional\CoreVersionUiTestTrait
Closed as a duplicate of 🐛 Fix tests (next minor) Active
The merge request updates 'assertEquals()' arguments in tests to expected, actual
The merge request adds support for Datetime Range field type and adds test coverage for the daterange field type
8.x-2.4 was released 7 April 2025
@rang501 can you create a merge request instead of uploading a patch? Working with merge requests is the preferred workflow
Let's close this issue as a duplicate of ✨ Missing schema tags for courses Active , so we can focus our efforts in the related issue.
Settings to 'Needs work' to fix the test failures
BC break reported in Editor Advanced Link: 🐛 D11.2: Uncaught CKEditorError: Cannot read properties of undefined (reading 'viewUid') Active
The merge request now include a custom Content Lock phpcs ruleset that excludes Drupal.Arrays.Array.LongLineDeclaration
Changes for Drupal.Arrays.Array.LongLineDeclaration were reverted.
Gitlab CI will pick up a custom phpcs configuration, as do IDEs like PHPStorm. Is Drupal.Arrays.Array.LongLineDeclaration the only rule that should not be enforced?
See webform for reference: https://git.drupalcode.org/project/webform/-/blob/6.3.x/phpcs.xml?ref_ty...
The merge request applies gitlab CI defaults for phpcs
Thanks!
Domain source uses the base_url option for its output. There is no need to add the Country path prefix anymore, as it is already available in the base url.
The 'external' option is not a supported key for outbound processing, so that can be removed.
BC break reported in Linkit: 🐛 Future compatibility fix for v45 of CKEditor5 Active
✨ Linkit for Link field Fixed introduced the link-widget-title--auto class that indicates the title was set manually and should not be overwritten
The regression was introduced in 10.4.x, but the fix is only available in 11.x. Any chance of a backport to 10.x?
The merge requests updates the Domain Source OutboundPathProcessor to not rewrite the outbound URL if the source domain is the active domain
Nice to fix an issue by removing code, thanks!
alexpott → credited idebr → .
I think it was a prerequisite for ✨ Release lock when browsing away from locked form RTBC and it has been enabled ever since
Oh I see.
The merge request works as expected, thanks!
Nice to see the CSRF token in place
What is the use for the destination query parameter in content_lock_js_url? This URL is only called in the background and not something a user actually visits?
I expected a CSRF token instead of a custom hash. Can you elaborate why the custom hash is preferred in this case?
The phpstan pipeline job findings are fixed in the merge request
The merge request implements compatibility with both Commerce 2.x and 3.x
This issue was reported earlier in 🐛 RuntimeException: Adding non-existent permissions to a role is not allowed. Needs review . See the related issue for a patch and possible workarounds.
I should have clarified the issue occurs when using the 'Lock form using JS' option.
I moved the test coverage to \Drupal\Tests\content_lock\FunctionalJavascript\ContentLockNodeTest::testContentLockWithTranslations with this option enabled so the issue is triggered correctly.
The stylelint pipeline job findings are fixed in the merge request
This was reported (and fixed) earlier in 📌 Nullable types must be explicit Active
I'll close this issue as a duplicate
This issue is being fixed in 📌 Fix phpstan pipeline job findings Active with a class alias
The phpstan pipeline job findings are fixed in the merge request
Claro is marked as internal and is allowed to break BC since https://www.drupal.org/node/2582945 → per https://git.drupalcode.org/project/drupal/-/blob/11.x/core/themes/claro/...
The merge request fixes the phpcs pipeline job findings
The merge request updates Claro's jQuery autocomplete enhancements to use (only) css
Works, thanks!
The merge request
- Removes outdated warning: Relying on a CDN for external libraries can cause unexpected issues with Ajax and BigPipe support
- Lowers the severity from error to warning as it was before 📌 Change the Webform libraries CDN warning to an error in the Status report (/admin/reports/status). Fixed
idebr → created an issue.
The merge request fixes the phpcs pipeline job findings
Drupal 11 compatibility was fixed in 📌 Drupal 11 compatibility fixes Active
Duplicate of 📌 Update CKEditor 5 to 45.0.0 Active ?
The merge request converts ExtraField plugin discovery to attributes
The merge request fixes the phpcs pipeline job
The merge request updates the project to consistently use LF line endings
This was fixed in 📌 Commerce 3.0 campatibility Active
A follow-up is available for the change in line endings, see 📌 Use LF line endings consistently Active
#12 Return a boolean is now still valid, but triggers a deprecation
MR 233 is patch #34