Skip to content
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

Allow permalinking with a fixed, version agnostic, URL to latest downloadable assets like .msi files #314

Open
mamift opened this issue Nov 14, 2024 · 0 comments

Comments

@mamift
Copy link

mamift commented Nov 14, 2024

Hello

Github allows permalinking to point to the always-latest release page (see here: https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases)

As of writing, the latest release asset for the MSI file is:
https://github.com/dotnet/cli-lab/releases/latest/download/dotnet-core-uninstall-1.7.550802.msi

However, to download it, it requires knowing the version of the latest release, in this case '1.7.x'.

My request is: can you rename the asset files (or add another alongside the existing MSI, TAR.GZ files) so it does not encode the version in the file name?

This allows me to write scripts in PowerShell for instance, to always download and install the latest version when a particular automation is run; any URLs can point to a single fixed URL and we'll always get the latest version. This is very similar to how the dotnet-installer.ps1 script is released: the latest can always be downloaded at https://dot.net/v1/dotnet-install.sh (see https://github.com/dotnet/install-scripts).

So for instance, my ideal outcome would be

  • Query a URL like this:
https://github.com/dotnet/cli-lab/releases/latest/download/dotnet-core-uninstall.msi
  • And it will pulldown the latest version of the MSI installer file for the dotnet uninstaller tool.

Currently, trying to hit https://github.com/dotnet/cli-lab/releases/latest/download/dotnet-core-uninstall.msi will just return a 404 error.

I confess I'm not sure if this is a limitation of GitHub releases or how this project is setup, but if someone could look into this, I'd appreciate it. I'm trying to install and run this tool automatically (on a schedule) on a bunch of on-prem servers we manage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant