Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,13 @@

https://github.com/user-attachments/assets/4c71c677-fcf5-4ab8-939c-0b26c579f175

**Download Bottleneck**

| Platform | Installer |
| --- | --- |
| macOS | [Apple Silicon (DMG)](https://github.com/areibman/bottleneck/releases/latest/download/Bottleneck-0.1.18-arm64.dmg) · [Intel (DMG)](https://github.com/areibman/bottleneck/releases/latest/download/Bottleneck-0.1.18.dmg) |
| Windows | [Installer (EXE)](https://github.com/areibman/bottleneck/releases/latest/download/Bottleneck.Setup.0.1.18.exe) |
Comment on lines +9 to +12

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid hard-coding versioned installer filenames as “latest” links

The README advertises links to the latest installers but the URLs include the explicit 0.1.18 file names. GitHub’s /releases/latest/download/<asset> only resolves when the named asset exists in the most recent release; once the next release is cut with different filenames these links will start returning 404s. Users following the README after a new release won’t be able to download the app. Consider linking to stable asset names or to the release page itself so the links remain valid across versions.

Useful? React with 👍 / 👎.


**Demo in action:**
https://screen.studio/share/o6sCO1uS

Expand Down