Expansion/legion

[vendethiel]

First commit contains my changes Second commit contains the libs.

I really want to ditch .pkgmeta for many reasons, most of which I explained in #1 already. .pkgmeta doesn't help with basically anything – it doesn't provide versioning, it has stale references to everything, and it encourages using a tool that no one uses. If anything I'd rather use git submodules. I also had to patch LibCooldownTracker to add per-spec cooldown overrides like legion has.

[vendethiel]

Ok, got the dashboard

[slaren]

Sure, do whatever you want with the issues. The build failed again: Unknown repository type, or unable to connect to repository. https://repos.wowace.com/wow/libdispellable-1-0

[vendethiel]

Yup, I saw it go through. No issue with reading through CI logs :).

I want to take the time to say "thank you" for your supervision even though you really have no reason to care at all, during this month-and-so.

[vendethiel]

Whoo! Seems like it turned green

[vendethiel]

Aaaand it works!

[vendethiel]

@slaren About to release as 1.0-beta.

[slaren]

Thank you for contributing to the project. It's the least I can do if someone is willing to contribute to my project rather than forking or starting their own.

You can have the packager make a release by creating a tag in the repository. There is some documentation about all this: https://www.curseforge.com/docs/packaging

[vendethiel]

Alright. Pushed a tag! Let's see.

[vendethiel]

Now I just need to figure out how to "push" the beta to mods.curse... Or do betas not get there?

[vendethiel]

Oh, is it because it's "under review"?

[slaren]

I am not sure why it is "under review", I guess some mod has to validate the project again.

[vendethiel]

It went through! 👍