Repository navigation
chore(release): release 1.0.0-beta.109 - #4923
ScriptedAlchemy merged 2 commits into
Conversation
|
72c06c0 to
c9eacf0
Compare
There was a problem hiding this comment.
Note
Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.
Devin Review found 1 new potential issue.
⚠️ 1 issue in files not directly in the diff
⚠️ Release binaries retain the previous version
Bazel builds of beta.109 still report beta.108 through CARGO_PKG_VERSION. The build script embeds beta.108, and run_upgrade uses it as the installed version. Direct-install users keep receiving upgrade offers for the installed release.
0d98c6d to
4f588a9
Compare
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
⚠️ 1 issue in files not directly in the diff
⚠️ Release binary retains the old version
For beta.109 builds, CARGO_PKG_VERSION remains beta.108 in the CLI and its build script. PRODUCT_BUILD_VERSION inherits that stale version. Users receive a mislabeled binary whose upgrade checks continue offering the installed release.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.0.0-beta.109 (2026-11-18)
Bug Fixes
This PR was generated with Release Please. See documentation.