I recently tested the addon with the retail version and everything works fine. Since the Interface APIs are basically the same now, I think this could be automated to always release the Classic and Retail AddOns together.

To deploy to curseforge and have it shown as compatible we need to update the Interface build number in Bam.toc to 80205 and do a separate deployment/tag-release

Possible ways to do this:

• Implement a github action that automatically creates a second release with the updated Interface number
• Manually change and upload the archive with the new build number (eurgh)

Needs investigation:

• How does curseforge behave eg. if the name of two releases is the same, just with a different build number
• Contact curseforge support and ask if they could implement a new replacement variable for the Interface build number. That way the second release could be triggered by an API call. There are already variables like @project-version@