• wants new signing config options in indra 3.1.0
• query the MC version manifest to see if new versions should be published
• query repo for existing published versions
• build one data version for all required MC versions in parallel
• only publish for stable releases

ideally for new MC releases this happens fully automatically, unless code changes are required (due to registry changes or sth)

This allows users to have data classes for multiple game versions on their classpath in parallel. The result would be something like:

• net.kyori:adventure-vanilla-data-1.16.5:1.0.0 with the package net.kyori.adventure.data.vanilla.v1_16_5
• and net.kyori:adventure-vanilla-data:1.0.0+1.16.5 with the package net.kyori.adventure.data.vanilla

both existing as artifacts