fix(proxy): bump pinned Meta-Proxy version to 0.4.1#145
Merged
Conversation
Meta-Proxy v0.4.1 (cognitum-one/meta-proxy#28) fixes a real bug: `meta-proxy login`/`logout` only ever wrote ~/.ruflo/proxy-config.toml on disk, which an already-running daemon (config loaded once at boot) never observed until restarted — a logout could even be silently undone the next time the daemon's cached OAuth token needed a refresh. v0.4.1 adds an internal reload endpoint that login/logout now call, so it takes effect immediately. The default `npx metaharness proxy install`/`proxy run` pin was still 0.4.0 (the pre-fix release), so every user without an explicit --version override was getting the buggy binary. Bumps META_PROXY_VERSION to match the signed 0.4.1 release already published to meta-proxy-dist, and bumps this package's own version in lockstep (matching the 0.3.2->0.4.0 precedent). Verified end-to-end: built this package, ran `proxy install --yes` with a fresh HOME (no version override) against the real signed release channel — installs, checksum + Ed25519 signature verify, and the binary contains the fix. Co-Authored-By: claude-flow <ruv@ruv.net>
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
meta-proxy login/logoutonly ever wrote~/.ruflo/proxy-config.tomlon disk. An already-running daemon (config loaded once at boot into memory) never observed that change until restarted — alogoutcould even be silently undone the next time the daemon's cached OAuth token needed a refresh. v0.4.1 adds an internal reload endpoint thatlogin/logoutnow call, so it takes effect immediately without a restart.META_PROXY_VERSIONpin here was still0.4.0(the pre-fix release), so every user runningnpx metaharness proxy install/proxy runwithout an explicit--versionoverride was getting the buggy binary.META_PROXY_VERSIONto0.4.1(already signed and published tometa-proxy-dist), and bumps this package's own version in lockstep — matching the existing0.3.2 → 0.4.0precedent from the last proxy-version bump.Test plan
npx tsc --noEmit— cleannpx vitest run __tests__/meta-proxy.test.ts— 6/6 passnpx vitest run(full suite) — 394/396 pass; the 2 failures (__tests__/bin-exit-code.test.ts) are pre-existing on unmodifiedorigin/main(verified by stashing this change and re-running), unrelated to this bumpnpm run build, then real e2e: fresh isolatedHOME,node dist/bin.js proxy install --yeswith no--versionoverride — installed, checksum + Ed25519 signature verified against the real public release channel, confirmed the installed binary contains the fix (reload-configsymbol present)🤖 Generated with claude-flow