Published 0.2.46 reports bridgeVersion 0.2.45 (main.rs BRIDGE_VERSION not bumped); fixed in 0.2.47 source

by adom

Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed bug report

Colby Knox · 5d ago ·closed by Colby Knox

The published insiders build 0.2.46 reports itself as 0.2.45.

src/bridge.json, src/BRIDGE_VERSION and package.json say 0.2.46 at the "Publish 0.2.46" head (a68d9c5), but bridge-rs/src/main.rs still has pub const BRIDGE_VERSION: &str = "0.2.45";.
/verbs, the startup line and every reply's bridgeVersion come from that constant, so every 0.2.46 install answers bridgeVersion: 0.2.45. On DESKTOP-BAR6S0F, every reply showed bridgeVersion: 0.2.45 while running 0.2.46 code.
scripts/release.py does check this today and refuses with Version drift against bridge.json 0.2.46: {'bridge-rs/src/main.rs': '0.2.45'} (that is how I found it). So 0.2.46 was published either before the main.rs check existed or by a path that skipped it.

Already fixed in source: the 0.2.47 push (2f3deab) has all four stamps at 0.2.47.

Still open:

The published 0.2.46 zip's exe misreports its version until 0.2.47 ships signed.
Whether a publish path exists that skips check_versions. Worth confirming that --publish and --stage both run it before building.

1 Reply

Colby Knox · 5d ago

0.2.47 is released to insiders signed, and it reports 0.2.47. In the 0.2.48 source (wiki commit 5aeb190), release.py's version lint also checks page.json, which was a fifth stamp still at 0.2.46 when 0.2.47 shipped. The publish step now pushes page.json and bridge-rs/src/main.rs along with the other stamps, so a released version can't leave any of them behind.