#specific module versions for specific foundry versions
latent mulch
when you get back, I'd appreciate some more pointers. I've done this, unless I'm misunderstanding (screen shot is from the 1.0.0 version and has been done for most, if not all, of them)
jolly mantle
Look in the Manifest URL for 1.0.0 as linked here: https://foundryvtt.com/packages/ffg-star-wars-enhancements
latent mulch
that points to the latest, which is what you said to do o.O
jolly mantle
No the download
latent mulch
oh do you mean edit the previous manifest URLs to point to the version-specific download?
jolly mantle
Yeah
latent mulch
so 1.0.0 would point to github release 1.0.0, not the generic module.json?
jolly mantle
I’m specifically (and only) referring to the download field here.
latent mulch
it looks like this is set up for the system, so I'll ask @fervent linden for help explaining how he did it. I'm not understanding how I'd end up with different copies of module.json
jolly mantle
Yeah if you’ve got like a release automation workflow going on, probably just needs a tweak somewhere.
fervent linden
I just tend to throw both the download zip and the system.json (at the time of the release) into the release assets, then point Foundry at those.
Not sure if that's best practice but seems to work
So it ends up always versioned, like
"manifest": "https://github.com/StarWarsFoundryVTT/StarWarsFFG/releases/download/v1.8-alpha7/system.json",
"download": "https://github.com/StarWarsFoundryVTT/StarWarsFFG/releases/download/v1.8-alpha7/starwarsffg_1.8.alpha7.zip",
Got a feeling that might be giving slightly rubbish UX for users though, as the manifest URL always "changes" with each release, which I think causes a popup in Foundry itself when they update.
jolly mantle
Yeah you can just make your manifests point at latest.
latent mulch
@jolly mantle if you have some time and interest to point me to docs or to a module/system doing this well, I'd appreciate it. don't want to leave my v9 users to fend for themselves 😅
jolly mantle
I won't have much time to dig into this today, but I recommend checking out this GitHub workflow template if you haven't already: https://github.com/League-of-Foundry-Developers/FoundryVTT-Module-Template/blob/master/.github/workflows/main.yml
latent mulch
I don't have any workflows set up but I'm down to play around and see if I can get it. will read through, thanks!
jolly mantle
lines 44 & 48 in particular there are what set the correct manifest and download URLs automatically for you
latent mulch
okay, I'm working on setting this up. let's say for a moment that I've managed to pull it off correctly. how does this tie in to the actual package management? do I use the same manifest URL for every version in the package manager, and Foundry magically figures things out?
latent mulch
nvm, read through the rest of the docs on that repo and figured it out. thanks again @jolly mantle !
jolly mantle
nvm, read through the rest of the docs on that repo and figured it out. thanks a...
Nice!
Super helpful addition to the release process, I've found.