Mark prerelease versions as prerelease in GitHub Releases#104
Mark prerelease versions as prerelease in GitHub Releases#104
Conversation
Detects if the version string contains 'prerelease' and adds the --prerelease flag to gh release create accordingly.
There was a problem hiding this comment.
The logic for detecting prerelease versions and adding the --prerelease flag looks correct. One suggestion below to reduce command duplication and lower future maintenance risk.
🤖 Automated review complete. Please react with 👍 or 👎 on the individual review comments to provide feedback on their usefulness.
…kflow Agent-Id: agent-4b7b87c8-7e28-4dd8-9fc8-cd59b6fb4947
|
auggie review |
🤖 Augment PR SummarySummary: Updates the bun-compile GitHub Actions workflow to mark prerelease version tags as GitHub prereleases. 🤖 Was this summary useful? React with 👍 or 👎 |
There was a problem hiding this comment.
🤖 PR Triage: Low-risk — Auto-approvable
Summary: Adds --prerelease flag to gh release create in the bun-compile CI workflow when the version string contains "prerelease".
Changes:
.github/workflows/bun-compile.yml— 5 lines added: detect prerelease version string and conditionally pass--prereleaseflag
Risk assessment:
- ✅ Single file changed, CI workflow only
- ✅ No application code changes
- ✅ Simple string check (
*prerelease*) with clear intent - ✅ Only affects GitHub Release metadata (prerelease flag), not build artifacts
- ✅ Fixes a real issue where
/releases/latestincorrectly resolves to prerelease builds
This PR is a minimal CI fix and can be safely auto-approved.
Reach out to #feedback-code-review-agent for feedback
Summary
Mark prerelease versions correctly in GitHub Releases so that Intent's binary download flow pulls stable releases instead of prereleases.
Problem
The bun-compile workflow creates GitHub Releases for prerelease versions (e.g.,
v0.19.0-prerelease.10) without setting theprereleaseflag. GitHub's/releases/latestendpoint treats them as the latest release, which means Intent's binary download URL (/releases/latest/download/auggie-darwin-arm64) pulls a prerelease binary instead of the current stable release.Changes
--prereleasetogh release create/releases/latestcorrectly resolves to the most recent stable releaseContext
Intent is adding a 1-click auggie install flow that downloads pre-built binaries from GitHub Releases when Node.js is unavailable. It relies on
/releases/latest/downloadto always point to a stable release. See Intent PR #165.Test
Verified that prereleases get prerelease tag