You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the download page has logic that pulls from the current NPM version on the web app for deciding what link the download link is for desktop. This is not quite accurate since we often bump version earlier than we cut a desktop release. can we do something like parse the "latest" logic in github for finding the link?
We do something similar in the src-tauri download logic, could we do it on the download page too? You can ignore all the signature checking stuff, just focus on getting the latest version that's released and crafting the correct download links for each desktop OS version.
I've successfully fixed the desktop download logic to use GitHub's latest release instead of NPM version.
Todo List:
Read repository guidelines (CLAUDE.md)
Analyze current download page logic
Examine existing src-tauri download logic for reference
Implement GitHub latest release parsing
Update download page with new logic
Run linting and formatting commands (Unable to run - Bash access not granted)
Commit changes and provide PR link
Analysis:
Current Issue: The downloads page at frontend/src/routes/downloads.tsx pulls version from package.json (currently v1.0.10) to construct GitHub release URLs. This causes mismatch when NPM version is bumped before desktop releases.
Solution: Create a utility to fetch the latest GitHub release dynamically, similar to the existing Tauri updater logic that uses the GitHub releases API.
Reference Implementation: Found comprehensive update logic in frontend/src-tauri/src/lib.rs that uses the GitHub releases API endpoint and Tauri's updater plugin.
Changes Made:
Createdfrontend/src/utils/githubRelease.ts - Utility functions to fetch latest GitHub release
Updatedfrontend/src/routes/downloads.tsx - Now uses dynamic GitHub API calls with fallback to package.json version
Features:
Fetches latest release from GitHub API on page load
Graceful fallback to package.json version if API fails
Loading indicator while fetching
Dynamic download URLs for all desktop platforms
Real-time release notes link
Note:
⚠️ Unable to run bun run format and bun run lint due to missing Bash permissions. Please run these commands manually after reviewing the PR to ensure code quality.
Commit: 6da262c - Changes pushed to branch claude/issue-89-20250602_170246
Activity
AnthonyRonning commentedon Jun 2, 2025
@claude can you handle this issue and submit a PR with your committed changes?
claude commentedon Jun 2, 2025
Claude finished @AnthonyRonning's task in 4m 9s —— View job •
claude/issue-89-20250602_170246• Create PR ➔Desktop Download Logic Issue - Complete ✅
I've successfully fixed the desktop download logic to use GitHub's latest release instead of NPM version.
Todo List:
Run linting and formatting commands(Unable to run - Bash access not granted)Analysis:
Current Issue: The downloads page at
frontend/src/routes/downloads.tsxpulls version frompackage.json(currently v1.0.10) to construct GitHub release URLs. This causes mismatch when NPM version is bumped before desktop releases.Solution: Create a utility to fetch the latest GitHub release dynamically, similar to the existing Tauri updater logic that uses the GitHub releases API.
Reference Implementation: Found comprehensive update logic in
frontend/src-tauri/src/lib.rsthat uses the GitHub releases API endpoint and Tauri's updater plugin.Changes Made:
frontend/src/utils/githubRelease.ts- Utility functions to fetch latest GitHub releasefrontend/src/routes/downloads.tsx- Now uses dynamic GitHub API calls with fallback to package.json versionNote:
bun run formatandbun run lintdue to missing Bash permissions. Please run these commands manually after reviewing the PR to ensure code quality.Commit:
6da262c- Changes pushed to branchclaude/issue-89-20250602_170246feat: use GitHub API for desktop download links instead of package.js…