fix(server): use BUNDLED_VERSION for app version in binary mode#1049
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR reduces the update-check cache staleness window from 24 hours to 1 hour and adds conditional version resolution logic based on build type. Binary builds use a bundled version constant; non-binary builds read from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
fix(server): use BUNDLED_VERSION for app version in binary mode
fix(server): use BUNDLED_VERSION for app version in binary mode
Summary
appVersionin the API routes readspackage.jsonviaimport.meta.dir, which is baked to the CI runner path in compiled binaries — always resolves tounknownunknownagainst the latest release and always shows an update badge, even when the binary is currentBUNDLED_VERSION(build-time constant) in binary mode, fall back topackage.jsonin devFiles Changed
1 file:
packages/server/src/routes/api.tsTesting
~/.archon/update-check.jsoncache (pointing at v0.3.2) should also be cleared by users or will expire after 24hSummary by CodeRabbit