[Bug] Doesn't recognize neoforge.mods.toml if neoforge dependency is omitted

[Kir-Antipov]

Description

Currently, mc-publish doesn't recognize neoforge.mods.toml as a valid NeoForge metadata file if it omits the neoforge dependency block (e.g., like it's done in Sodium):

[[dependencies.example-mod]]
    modId="neoforge"
    versionRange="[34,)"
    ordering="NONE"
    side="BOTH"

This check was only relevant before NeoForge diverged from using the same mods.toml as legacy Forge. Nowadays, the mere existence of neoforge.mods.toml is a sufficient indicator that the mod supports NeoForge.

Expected Behavior

mc-publish should be able to read neoforge.mods.toml even if it doesn't explicitly specify the neoforge dependency block.

Actual Behavior

mc-publish fails to read neoforge.mods.toml if the neoforge dependency block is omitted, effectively disabling automatic property resolution.

Version

v3

Environment

GitHub Actions

Configuration

No response

Logs

No response

Other Information

No response

[Faboslav]

Hello there, is there any progress on this? It would be nice to have dependency recognized without the need to specify them in the CI

[Kir-Antipov]

Hi! Yup, there definitely is! I believe I've fixed/implemented almost everything related to the issues in this repo in my local tree (except for Hangar and stuff like that). However, I'm currently in the midst of migrating mc-publish to a new runtime (and containerizing it along the way), because I'm quite frustrated with how GitHub handles Node.js actions; and I've been also dealing with some IRL stuff, so yeah, I definitely took my sweet time with this update xD I hope to finally release v4 before Mojang drops 1.22 on us :)

[Faboslav]

@Kir-Antipov Anything that can be helped with in the mentioned PR?