Contrib.social

Prepare for package_manager in core

Open on Drupal.org →
Created on 31 October 2024, 5 months ago

Problem/Motivation

After ✨ Add Alpha level Experimental Package Manager module Needs review package_manager will hopefully be beta/rc/stable in Drupal 11.2.0, and if not stable by then, potentially stable in a patch release or early in 11.3.

When automatic_updates is installed, then version of package_manager from the contrib module will take precedence due to how Drupal core module discovery works.

However when package_manager is stable, we will want sites using the contrib module to use the core version of package_manager, not the one shipped with this module.

I think that the process could look something like this, and might be OK without too many complications, however it would be good to get confirmation on any of these points and we should try to test them in practice as soon as possible.

1. Once package_manager is stable in core, release a version of automatic_updates without package_manager included, that depends on the core version containing stable package_manager. This would literally be a an rm -rf of the module from the contrib repo.

2. Automatic updates should update itself to this new version.

3. At this point, the composer update of automatic_updates is going to remove packagei_manager from the contrib directory. And the next request, package_manager in core will immediately take over.

If #3 works that is great. If it does not, no idea what will happen.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

3.1

Component

Code

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @catch
  • Comment 5 months ago →
    🇬🇧United Kingdom catch

    Trying to think through how we could test what will actually happen, I think it is:

    1. Release a very early alpha of 11.2 as soon as package_manager reaches beta stability.

    2. Start a new major branch of automatic_updates with package_manager removed, release an early alpha of that.

    3. Either in core or package_manager add a hidden/testing module that removes all the guardrails about minor/major updates and alpha/beta/rc releases,

    4. Take an 11.1 site with automatic_updates, then using automatic updates, update it to 11.2.x and the new major automatic_updates branch.

  • Comment 5 months ago →
    🇬🇧United Kingdom catch

    Writing #2 makes me realise this needs to be a core issue for the early alpha release, especially if we want to test this while package_manager is alpha instead of beta to iron anything out earlier. We can then spin off an issue for automatic_updates once we've figured out the steps.

    Once we have one early alpha release, we can also test core package_manager updating core to a second early alpha release, so this issue will cover both of those things.

  • Comment 5 months ago →
    🇳🇿New Zealand quietone
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024