PowerShell / PowerShell/Win32-OpenSSH
Make deep links to latest *.msi release files possible by removing the version from the filename
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Summary of the new feature / enhancement
As a developer, I want to directly link the Windows Installer File (MSI) of the latest Win32-OpenSSH release, so that I can simplify update instructions and automation.
This is currently not possible due to the filename that contains the specific version.
I suggest removing the version number from the filename, so that OpenSSH-Win64-v9.4.0.0.msi becomes OpenSSH-Win64.msi and therefore the following deep link will always resolve the latest installer:
Only the MSI filenames need to change. The other files can be reached like:
Proposed technical implementation details (optional)
See also: https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the release packaging configuration that determines MSI asset names; the issue does not identify a file or entry point. Confirm the change by checking that the latest release exposes OpenSSH-Win64.msi and that the existing ZIP asset remains available at its documented deep link.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100