Add a new CI job that creates a core version of Automatic Updates and Package Manager, and runs their tests

How can we run this against 10.1.x with the contrib version to make sure it still passes?

Ideally 3.0.x would be tested against both 10.2.x and 10.1.x but at the least I think we need be able to test before commit.

As with Drupal CI, it is possible to trigger a pipeline manually against a different branch of core (in the case of 10.1.x, that would be $CORE_SECURITY_PREVIOUS_MINOR). You can also do that for branches in an issue fork.

It's a tad cumbersome, but not much worse than what we had to do with Drupal CI. Remember:

• It only tested one branch automatically on commit (GitLab CI is the same way)
• If you wanted to test it against a different branch, you had to fill out a form to do that (same thing with GitLab CI)

Merged [#3415403}

Working on patch failures in conversion

Tests are on passing now on the module converted to the core version and testing as part of core 11.x!

I'm pretty happy with this. A few minor points.

The last test failure was actually because of core issue 📌 Fix root namespace classes DebugClassLoader forward compatibility warnings Needs work that was since reverted. It caused an incompatibility with Core 11.x and php 8.3.

Running the tests again, I think it should pass now

@phenaproxima I think I have addressed your points and the tests should pass now that 📌 Fix root namespace classes DebugClassLoader forward compatibility warnings Needs work has been reverted

I worked a lot on this so I might not be the one to RTBC it, but I'm doing so anyway. I think this looks good. With this change, we're really covering all our bases with tests and it makes verifying the core merge request a lot easier.

@phenaproxima thanks. I agree this is really good to add test coverage for the conversion and testing as the core module!

Automatically closed - issue fixed for 2 weeks with no activity.