Problem/Motivation

#3307163: Add the ability to ProjectInfo handle projects not in the active codebase in we added our own Update processor so that we fetch XML for new projects

Now that we have that it might make sense to use for all projects so that the cache time is not affected by how often the site admin wants available updates to be checked.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork automatic_updates-3308235

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

tedbow created an issue. See original summary.

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Issue tags: +core-post-mvp
tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Version: 8.x-2.x-dev » 3.0.x-dev

tedbow opened merge request !965

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Priority: Normal » Major
Status: Active » Needs work
Issue tags: -core-post-mvp +core-mvp
Related issues: +#3394754: [policy, no patch] Use Update XML in Package manager to determine release support status

To accomplish the plan in #3394754: [policy, no patch] Use Update XML in Package manager to determine release support status we will probably need to the current issue.
Especially this part:

We should also check that the available versions returned by the Update XML, just the numbers not the metadata unknown to Composer, match the available versions as known to Composer (composer info -a).

If are going to check against versions know by release we can't rely an old version of the update xml or they might be out of sync.