Hi, I play WoW on Linux and use a nifty opensource tool called strongbox to keep track of addons. It allows you to specify github links instead of curseforge links in order to keep addons updated, as long as the github page in question ships Releases.

However, WeakAuras seems to include only Classic in Releases on github, with TBC nowhere to be found. This has forced me to revert back to curseforge for keeping track of WeakAuras2. Would it be possible to include the TBC version under Releases? A popular addon that does this is Questie.

Anyway, thank you for your time and for the amazing work that all of you have done.

@SpatenLa Huh! That's weird. I wonder why strongbox isn't picking up the release. Thank you for entertaining my request.

@SpatenLa Gotcha. Thank you! I will open a ticket with the Strongbox people. :-)

@SpatenLa , thanks for taking the time to look into @jecs problem.

the official name supported by blizzard, the addon pages and the packager is bcc

I've seen a lot of variation so far but not much/any usage of bcc so I didn't think to add it to the matcher. Do you have a link or citation or something for the official usage of bcc ? cheers.

This should answer your question
Stanzilla/WoWUIBugs#68 (comment)
https://github.com/BigWigsMods/packager#build-type-keywords

that's a very interesting link, @mrbuds , thankyou. The conversation around which abbreviations to support was kind of funny ;)

From the linked comment

The implementation we've been informed about is as follows:

Is this a secret channel of information leaked to the public by Blizzard or do Blizzard have technical documentation on upcoming client changes somewhere that I can read (from the horse's mouth so to speak)?

You can talk about it at https://discord.gg/h7WSRf8 i'm gonna close this as it's gone too far offtopic for this bugtracker.