Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Enabling deprecation notices will identify anything we need to adjust prior to D9 and make sure we stay compatable.
Proposed resolution
Add drupalci.yml file to enable deprecation notice, and fix any issues.
Remaining tasks
User interface changes
none
API changes
none
Data model changes
none
Release notes snippet
Comment | File | Size | Author |
---|
Comments
Comment #2
mikelutzJust wanted to see what this looks like.
Comment #3
heddnVery good idea.
Comment #4
mikelutzCool. :-) fixed the lack of newline, but we should add this to ALL the modules. :-)
Comment #5
heddnI've merged in some changes I've seen elsewhere. Let's see if this also works.
Comment #7
mikelutzComment #8
mikelutzComment #10
heddnThat's confusing. We're doing very similar to https://cgit.drupalcode.org/jsonapi/tree/drupalci.yml
Comment #11
heddnComment #13
heddnComment #14
heddnComment #17
heddnComment #19
heddnYeah, it passes.
Comment #20
heddnSeems like the JS tests are failing. Possibly because we have no js nor js tests. Let's fix that.
Comment #23
heddnMore errors are surfacing. https://www.drupal.org/pift-ci-job/1151068
Comment #25
heddnHopefully the fixes for https://www.drupal.org/pift-ci-job/1151089
Comment #26
heddnGoing to leave this as fixed. But this was a good exercise. We found #3021538: $migration->get('migration_group') causes deprecation warnings.
Comment #28
Kristen PolPer a Slack discussion with Gábor Hojtsy regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing tag cleanup here based on that discussion.