Closed Iggle closed 2 years ago
hey @Iggle , thanks for opening a ticket (you have a great avatar ;)
Yes, you're correct, Strongbox doesn't support MythicDungeonTools because it doesn't upload assets to their tagged releases.
Under Github, an asset zip file shows up fine.
Github will automatically create a .tar.gz
and a .zip
for each tagged revision, which is what you see here:
But Github doesn't consider these assets. It calls them tarballs and zipballs, but not assets [in the API].
Further, the folder structure of these zipballs can't be used because the folder name Github uses to bundle the files up contains the tag value:
Also, some addons also need a pre-processing of the addon files before creating a release as often there are templates to be rendered or files to be generated.
As of Strongbox 5.2.0 you can download the zip file and use File -> Install addon from file
but it (probably) won't be matched against a catalogue and won't know where to go to find updates. If in the future MDT start uploading assets to their Github releases and we add MDT to the Github catalogue, then an addon installed this way may automatically find a match and start receiving updates.
I would recommend you open a ticket on MDT and ask them to modify their development workflow to include uploading assets to Github when they do a release.
If MDT start uploading assets, feel free to mention it on the Github catalogue ticket: https://github.com/layday/github-wow-addon-catalogue/issues/4
Hope this helps.
Describe the bug The MythicsDungeonTools Repository does Release Tagging just fine, but the "assets" section in the API is empty. Under Github, an asset zip file shows up fine. If passed to
strongbox.zip/valid-addon-zip-file?
, strongbox is happy with the structure.To Reproduce Steps to reproduce the behavior. For example:
Expected behavior Zipfile should be downloaded from
archive/refs/tags/<semver>
Additional context A MDT Release looks like this in
strongbox.github-api/download-release-listing
: