Pin the VibeMon installers to the 0.2.13 binary they ask for - #25
Merged
Conversation
The 0.2.12 and 0.2.13 scripts passed --profile messages to a pinned 0.2.11 binary, so every new install failed at pairing (report #86). The pins move with the workspace version and a test keeps them together. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…regexes are multiline Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/migration/vibemon-install.sh/.ps1:ATTEMPTDB_VERSION0.2.11 → 0.2.13,INSTALLER_VERSION0.2.13+install.1, shINSTALLER_REF→ the hotfix taginstall-2026-09-09.1(for the Windows hand-off).--profile messagesto a pinned 0.2.11 binary →unknown profile messages→ "pairing failed". Every new install since the web pin moved to v0.2.12 fails the same way; existing devices are untouched by the failed step.tests/installers/test_pins.pypins both scripts to the workspace version (runs in the "migration installer regressions" job).Test plan
python3 -m unittest discover -s tests/installersinstall-2026-09-09.1on main and point vibemon-webATTEMPTDB_INSTALLER_REFat it🤖 Generated with Claude Code