[GH-ISSUE #5604] [Bug] wrong download link in winget's repo #2492

Closed
opened 2026-03-23 21:22:52 +00:00 by mirror · 4 comments
Owner

Originally created by @orkeilius on GitHub (Jun 22, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5604

Bug Description

Wrong download link for 0.6.1
(there is a "v" in the version that shouldn't be here)
https://github.com/AppFlowy-IO/AppFlowy/releases/download/v0.6.1/AppFlowy-0.6.1-windows-x86_64.exe

How to Reproduce

install/update appflowy with winget

Expected Behavior

the link should be

https://github.com/AppFlowy-IO/AppFlowy/releases/download/0.6.1/AppFlowy-0.6.1-windows-x86_64.exe

Operating System

windows

AppFlowy Version(s)

0.6.1

Screenshots

No response

Additional Context

No response

Originally created by @orkeilius on GitHub (Jun 22, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5604 ### Bug Description Wrong download link for 0.6.1 (there is a "v" in the version that shouldn't be here) https://github.com/AppFlowy-IO/AppFlowy/releases/download/v0.6.1/AppFlowy-0.6.1-windows-x86_64.exe ### How to Reproduce install/update appflowy with winget ### Expected Behavior the link should be https://github.com/AppFlowy-IO/AppFlowy/releases/download/0.6.1/AppFlowy-0.6.1-windows-x86_64.exe ### Operating System windows ### AppFlowy Version(s) 0.6.1 ### Screenshots _No response_ ### Additional Context _No response_
mirror 2026-03-23 21:22:52 +00:00
Author
Owner

@orkeilius commented on GitHub (Jun 22, 2024):

Issue in the winget repos : https://github.com/microsoft/winget-pkgs/issues/159413

<!-- gh-comment-id:2184188372 --> @orkeilius commented on GitHub (Jun 22, 2024): Issue in the winget repos : https://github.com/microsoft/winget-pkgs/issues/159413
Author
Owner

@Dragon1573 commented on GitHub (Jun 23, 2024):

@AppFlowy-IO - Since the package is released directly on GitHub Releases, would you consider take full control of your package manifests on microsoft/winget-pkgs, with automatically submitting manifests with WinGet Releaser v2? This can keep manifests always up to date once a new version is released. 🙏🏼

<!-- gh-comment-id:2184408422 --> @Dragon1573 commented on GitHub (Jun 23, 2024): @AppFlowy-IO - Since the package is released directly on **GitHub Releases**, would you consider take full control of your package manifests on [microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/AppFlowy/AppFlowy), with automatically submitting manifests with [WinGet Releaser v2](https://github.com/marketplace/actions/winget-releaser)? This can keep manifests always up to date once a new version is released. 🙏🏼
Author
Owner

@LucasXu0 commented on GitHub (Jun 23, 2024):

@Dragon1573 the version was correctted a few day ago.

AppFlowy-IO - Since the package is released directly on GitHub Releases, would you consider take full control of your package manifests on microsoft/winget-pkgs, with automatically submitting manifests with WinGet Releaser v2?

Sure, we can integrate the WinGet Releaser into our CI release job.

<!-- gh-comment-id:2184900017 --> @LucasXu0 commented on GitHub (Jun 23, 2024): @Dragon1573 the version was correctted a few day ago. > AppFlowy-IO - Since the package is released directly on GitHub Releases, would you consider take full control of your package manifests on microsoft/winget-pkgs, with automatically submitting manifests with WinGet Releaser v2? Sure, we can integrate the WinGet Releaser into our CI release job.
Author
Owner

@orkeilius commented on GitHub (Jun 24, 2024):

Fixed and closed in winget's repo

<!-- gh-comment-id:2186917803 --> @orkeilius commented on GitHub (Jun 24, 2024): Fixed and closed in winget's repo
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#2492
No description provided.