9.0.0+1.21.11-neoforge

Breaking Changes

Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which will have broken pretty much any mod with a compile-time dependency on Patched. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s).
Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes here.

Added the /patched trace <file> command (also works with /patchedc), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is actually applying to a file without needing to read through a (possibly massive) json file from /patched dump file. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!)
Added absolute paths and placeholders. See also the updated path documentation here.
Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their _dummy.json files, if present.

On Fabric, custom test conditions and data sources can now be registered using ObjectShare. See the documentation for details.

Patches dumped using the wrong-sided command (e.g. /patched dump ... on a patch in assets) will now dump normally rather than cryptically failing.
Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once).
The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding -Dpatched.debug to your JVM arguments.
Fixed pack_enabled test condition erroring when no dynamic patches are present.