-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta: Automate detection + build of new Foundry releases #793
Comments
I like this idea, and have thought about doing something like this. The first step was to find an API or other data source that has all the FoundryVTT releases. I haven't been able to find such a list. I was hoping the download page on foundryvtt.com made such a call to populate its drop-down list, but I think it is generated server-side. This probably won't be too high of a priority feature request as there is a really good work-around already: |
Idk if this is an isolated issue on my end, but whenever I've tried that
workaround (which is great btw, not complaining), I end up with the
software believing that it's version number is "undefined"?
…On Fri, 29 Sept 2023, 00:53 Mark Feldhousen, ***@***.***> wrote:
I like this idea, and have thought about doing something like this. The
first step was to find an API or other data source that has all the
FoundryVTT releases. I haven't been able to find such a list. I was hoping
the download page on foundryvtt.com made such a call to populate its
drop-down list, but I think it is generated server-side.
This probably won't be too high of a priority feature request as there is
a really good work-around already:
- #796 <#796>
—
Reply to this email directly, view it on GitHub
<#793 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACHF4SGFPZS2QC72UWS3ULX4YEZDANCNFSM6AAAAAA5LNRTCM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Feature description
Timed builds, which track changes to https://foundryvtt.com/releases/ and look for new releases.
When a change is detected, a new build could be kicked off automatically as a release candidate using the previous build as a template, this would reduce the number of requests for new builds in the days to weeks following a new Foundry release.
Motivation
Example
Currently there is a fresh version to deal with an exploit in the self-hosted provider. This has prompted a number of modules to force minimums of the new version. There are little to no changes for NodeJS based instances, but we're stuck unable to install modules until this is fixed.
Pitch
Optimizing the build pipelines of this project can't really go anywhere else.
Code of Conduct
The text was updated successfully, but these errors were encountered: