Skip to content

4.8.0
Compare
Choose a tag to compare
@torkus torkus released this 12 Dec 13:28
· 406 commits to develop since this release
4.8.0
0c43307
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Added

  • Gitlab support.
    • similar to addons hosted on Github, Gitlab addons must be using releases with custom assets (not the default ones).
  • multi-toc support.
    • the presence of multiple .toc files determines if an update is necessary when switching game tracks.
    • a warning is issued if the suffix of a .toc file doesn't match the Interface Version within it.
      • for example, SomeAddon-Classic.toc is using a 20501 as it's interface version.
      • this may lead to false positives for the few addons that are named SomeAddon-Classic and use multiple toc files.
    • a warning is issued if there are multiple non-identical sets of toc data for the same game track.
      • for example, an addon has SomeAddon-Classic.toc and SomeAddon-Vanilla.toc (both valid), but -Vanilla.toc data is not identical to -Classic.toc.
        • in these cases the first in the group is used with '-Classic' having alphabetic priority over '-Vanilla', '-BCC' over '-TBC', etc.
  • release.json support for Github and Gitlab.
    • this file is generated by Bigwigs packager and includes extra information about files in a 'release'.
      • a 'release' is a bundle of files, including the addon zip file, in Github and Gitlab attached to a revision tag.
    • it is being used to find the supported game tracks for a release if they can't be guessed in any other fashion.

Changed

  • the 'source-id' column in the GUI has had it's max width removed.
    • this is because Gitlab addons can have very long IDs.
  • Github addons are no longer assumed to be for retail/mainline unless released prior to the release of Classic.
  • Github addons will now do extra checks to determine game tracks for the latest release, on initial import and during the user-catalogue refresh.
    • if absolutely no game tracks can be found we default to retail.
      • this may be replaced in the future by actually downloading a release and inspecting it's contents
  • http downloads will no longer be re-attempted on client (4xx) errors, server (5xx) and connection errors only.
    • this fixes the multi-second pause before an error while updating addons that have gone away.

Fixed

  • a minor bug in translating an interface version (10100) to a game track ("classic").
    • a bad value might have caused a stacktrace in the console
  • stability improvements to the 'refresh user catalogue' feature.
    • 404s, transient server errors and unhandled exceptions will no longer stop the update process.
Assets 6
Loading