It does not work

If you would like help, please provide more information, such as the contents of factorio-current.log. First ensure the mod is properly installed and enabled.

I can share you guys with more detailed information. I have the similar trouble.

factorio | 0.018 Error Util.cpp:81: Failed to load mod "AutoDeconstruct":
factorio | • AutoDeconstruct
factorio | • Dependency base >= 2.0.57 is not satisfied (active: base 2.0.55)

It occurs with the last stable version of Factorio 2.0.55 and Auto Deconstruct 1.0.7.

It seems like this mod is not for the stable version now.

That error message is very self-explanatory and is operating correctly. If you are running Factorio 2.0.55 and use the in-game mod browser, it will automatically download the latest compatible version of Auto Deconstruct, which is 1.0.5. The in-game browser will not allow you to download incompatible versions. When 2.0.57 or later is marked stable, and you update to it, then it will allow the upgrade to Auto Deconstruct 1.0.6 and later.

Interestingly, even though the logs indicate an attempt to only download the latest version of Auto Deconstruct for 2.0.55, the mod auto-updater script for https://github.com/factoriotools/factorio-docker pulled this new version that requires base>=2.0.57, and so now my headless/dedicated server no longer launches.

Looking at the downloads tab here on the Mod Portal, I see the Factorio version set to just 2.0 (this seems to be the case for most mods I've poked at trying to see what values were common in that field)... I suppose it's not possible to be any more specific than that at the API level, is it?

There's a related issue already open on the Docker container's tracker, https://github.com/factoriotools/factorio-docker/issues/553, where they talk about wanting to figure out a "better" compatibility validator in the downloader. I'm mostly mentioning this as info for anyone else who gets bitten by this update and ends up with a non-starting Docker container while 2.0.55 is still the latest :stable image we can pull, it's not robot256's fault per-se.

I'm not familiar with the details of the mod portal API, but it should be possible to retrieve the dependency list and check the required version of "base" for each mod.

Edit: One of the API endpoints provides the entire text of info.json. This can be directly parsed to get the version of "base" required.