-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[FEATURE REQUEST] Consistent "latest" link directly to binary firmware #4337
Comments
The nightly/development builds would be very helpful. At the moment I can't run the latest build of MK3S firmware because it is expecting MMU2 build 3.0.1 but we only have access to 3.0.0 provided with release https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.13.0. |
Someone could probably PR in a Github action to do this, I suspect that it could update a few different URLs in a template then push to GitHub pages or something. |
The link https://github.com/prusa3d/Prusa-Firmware/releases/latest will always show you the latest stable release. |
Please DON'T USE the octoprint firmware updater as it is missing the OctoPrint/OctoPrint-FirmwareUpdater#325 to flash the MK3/S/+ correctly. Flashing firmware is only supported via Prusa Slicer |
The releases/latest works for the latest release but the filenames inside the release artifacts aren't stable |
We are not going to change the filenames as users may need to downgrade. Using same file name would result in multiple files with same name and an extra number behind when downloaded. There is no way for the user to find the correct version or the user has to create a folder for each version and this is not going to happen. |
I suppose every other software distribution on the planet offering predictable download URLs is just doing it wrong. |
Using software like octoprint firmware updater, there is the option to "remember URL", this is not very useful since there is no stable URL to pull the latest version of firmware from. I propose that there be a way to automate downloading the most recent (stable, dev, etc) build of the firmware for a device, which I believe would most easily come from creating some supplementary URLs that correspond to each release channel and device.
The text was updated successfully, but these errors were encountered: