Problem/Motivation

Drupal 10.2 security coverage ended in December 2024 when Drupal 10.4 was released.

Drupal 10.3 introduced some additional config validation features that would be useful for this module (see #3493946: Configuration schema not fully validate-able).

Steps to reproduce

Proposed resolution

Change the minimum core version for this module to 10.3 ahead of the release of 2.1.0.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork user_expire-3499521

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

joegraduate created an issue. See original summary.

joegraduate’s picture

joegraduate
Primary language English
Location Arizona, USA
CreditAttribution: joegraduate at The University of Arizona commented
Issue summary: View changes
Related issues: +#3493946: Make configuration schema more validate-able
joegraduate’s picture

joegraduate
Primary language English
Location Arizona, USA
CreditAttribution: joegraduate at The University of Arizona commented
Status: Active » Closed (duplicate)
Related issues: -#3493946: Make configuration schema more validate-able +#3495118: Increase minimum core version to ^10.3, add D12 support

Oops, we already did this in #3495118: Increase minimum core version to ^10.3, add D12 support.