The supported_formats and the formats fields in pack.mcmeta causes packs to be incompatible and prevents overlays from loading respectively

When I was working on updating one of my resource packs to support the new changes to the pack format system, I ran into an issue with the supported_formats field. As the change log of snapshot 25w31a states, “If your pack declares support for a pack version with the previous format (data pack < 82, resource pack < 65), [supported_format] is still required“, and in my scenario of a resource pack that (tries) to maintain compatibility all the way back to 1.14 with a single pack, I should still declare the aforementioned field. However, it seems as though the field being present automatically marks the resource pack as incompatible, proven by the log throwing an error:

Couldn't load file/test pack metadata: Pack key supported_formats is deprecated starting from pack format 65. Remove supported_formats from your pack.mcmeta.

While this would ordinarily not be a massive issue for me, my resource pack makes use of overlays which also rely on said format declaration, albeit using the “format” field which the issue present extends to; While not marking the pack as Incompatible, overlays with the format field do not load. As you may guess, this is pretty bad for backwards compatibility as it means you will need to make an entirely new resource pack that supports the new format.

Steps to reproduce the issue with a resource pack

• In Minecraft’s resourcepacks folder, create a new resource pack with a pack.mcmeta file included

• Open a text editor and paste the following text into the file:

  {
    "pack": {
      "pack_format": 65,
      "supported_formats": {
        "min_inclusive": 50,
        "max_inclusive": 64
      },
  	"min_format": 65,
  	"max_format": 67,
      "description": "test"
    }
  }

• Observe the resource pack on the Select Resource Packs screen

Expected result

• The resource pack is compatible and functions normally

Actual result

• The resource pack is labeled as Incompatible contradicting what the change log says should work