Problem/Motivation

The module cannot be installed in Drupal 12, due to the constraints in the *.info.yml files.

It works well, so it should be safe to expand the constraints to include Drupal 12.

Steps to reproduce

Try to install the modules in Drupal 12 and get an error:

$ drush install admin_navigation admin_navigation_position admin_navigation_tools
In ModuleInstaller.php line 119:
  Unable to install modules: module 'admin_navigation' is incompatible with this version of Drupal core.
Failed to run drush install admin_navigation admin_navigation_position admin_navigation_tools: exit status 1

Proposed resolution

We could allow installing the Admin Navigation modules in Drupal 12.

Remaining tasks

Update constraints, and perhaps also create a dev-branch to test changes in, like https://www.drupal.org/project/pathauto has 8.x-1.x-dev:

  • Update relevant *.info.yml files
  • Create a dev-branch (1.x-dev?) for testing new code

User interface changes

API changes

Data model changes

Issue fork admin_navigation-3615821

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

ressa created an issue. See original summary.

ressa opened merge request !1

  • 426d54f1 committed on 1.1.x 
    Issue #3615821: Allow installing on Drupal 12

Widen...
nelo_drup’s picture

nelo_drup commented

I implemented this directly on
1.1.x before seeing the fork, sorry for the duplicated effort — the change is
the same one you proposed.

Before widening the constraint I checked that nothing in the code stands in the
way: the only core dependency is Navigation (stable and in the standard profile
in Drupal 12), and the four procedural core functions still in use — base_path,
drupal_flush_all_caches, drupal_static_reset and views_invalidate_cache — are
not deprecated. Core's policy of deferring disruptive deprecations to 13.0.0 is
what makes one branch serve both majors.

All five modules now declare ^11.2 || ^12. The lower bound stays at 11.2
because OrderAfter and the #[Hook] order argument arrive in that release.

Released in 1.1.2.

On the dev branch: one already exists — 1.1.x-dev, generated automatically from
the 1.1.x branch. And thanks for spotting the default branch in GitLab, it is
now set to 1.1.x.

ressa’s picture

ressa
he/him
commented

Thanks for the fast release already, I can now download it without using mglaman/composer-drupal-lenient, and install it without https://www.drupal.org/project/backward_compatibility, awesome! And thanks for checking thoroughly that the code is Drupal 12-ready.

And about 1.x-dev, you're right, it was already there ... What I really meant, but did not clarify, is that it is not shown on the project page, like for https://www.drupal.org/project/pathauto:

Development version: 8.x-1.x-dev updated 4 Jul 2026 at 11:26 UTC

... and under https://www.drupal.org/project/pathauto/releases, "pathauto 8.x-1.x-dev" is listed.

For Admin Navigation, 1.x-dev seems to be not released. It is not listed under https://www.drupal.org/project/admin_navigation/releases, so I cannot select 1.x-dev under "Version", when I create a new issue.

ressa’s picture

ressa
he/him
commented
Assigned: ressa » Unassigned