Version 2.0.0-alpha1 is incompatible with Drupal 9.5.4.

Yeah just assume it is for Drupal 10 only.

Since the dependency Dynamic Entity Reference pulled a fast one a few months ago and made everything a hard Drupal 10 only.
Screwed up four modules I'm using that depended on that code.

(sigh)

8.x-1.1 GUIs work but the core detection classes fail completely generation 1000s of issues in watchdog.

Sadly don't have a viable alternative.. have to use 3rd party web crawelers I guess.

Please try this one.
That should work.

I think it should only add ^2.0? Adding ^1.16 might introduce incompatibilities.

reviewed the issue on Link Checker module on D9.5, MR !41 is good , no issue found after installation.
Moving to RTBC. Thanks

For those who want to use this module in version 2 on Drupal 9, until the MR is being merged, you can add a repository and requirement to your composer.json like this:

"repositories": {
    "drupal/linkchecker": {
      "type": "git",
      "url": "git@git.drupal.org:issue/linkchecker-3346793.git"
    },
    ....
},
"require": {
  ....
  "drupal/linkchecker": "dev-3346793-version-2.0.0-alpha1-is as 2.0"
}

Since DER is using triggers in Version 2 and 4 the dependency of Linkchecker to DER is very problematic in my opinion: #3193254: using dynamic_entity_reference brings in triggers and uninstalling does not get rid of them

Because of the trigger problematic I don't want to test something with v2/v4 of DER and others need to report about this. The reported Problem. was with v2 of DER.

I don't want to block people/projects who like to use v2/4 of DER but I would feel better if we just depend on v3 if v1 wouldn't work anymore as reported in #6.

We don't have a real code fix just to "open" the composer dependency. When @DamienMcKenna is right we can use this:
"drupal/dynamic_entity_reference": "^2.0 || ^3.0 || ^4.0"

This will still allow DER v2/v4. But I strongly recommend v3.

@all testers: Please report which versions of DER and Core you are using. And again: I will not spend any time to test DER v2/v4 setups.

This Issue is just another reason for me to get rid of this DER dependency and I will discuss this with the other maintainers.

@DamienMcKenna: Can you share a link or maybe explain what's the problem with DER 8.x-1.16?

Because DER v3 is only working with D10+ we need a solution for this, too.

Please report which versions of DER and Core you are using.

Core 9.5.10
DER 8.x-1.16

No issues so far.

This Issue is just another reason for me to get rid of this DER dependency

Quite understandably. Features that may depend upon DER should be extracted into their own integration module. That makes dependency management so much easier.

I can't find the issue right now, but I have previously argued that our dependency on it is there only for that very tiny little functionality, so we could instead just duplicate the parts we need from it. It really is not a lot to duplicate, and the module would be much easier to maintain :)

@eiriksm Maybe we only discussed this in a chat :-)
I added a new Issue for that: #3375553: Remove Dynamic Entity Reference (DER) dependency

For the original purpose if this issue, I'm setting this to RTBC so that it can be merged and people can then use the 2.x alpha release more easily.

I have rebased the MR for the latest changes in 2.0.x

Any chance that this minor change gets committed? Even if not required long-term, it would just solve an issue without the chance of breaking anything.

Thank you! Committed! 🥃