Bump @cryptohopper/sdk to ^0.4.0-alpha.2 (auth header fix)#9
Merged
pimfeltkamp merged 3 commits intomainfrom Apr 28, 2026
Merged
Bump @cryptohopper/sdk to ^0.4.0-alpha.2 (auth header fix)#9pimfeltkamp merged 3 commits intomainfrom
pimfeltkamp merged 3 commits intomainfrom
Conversation
The CLI's underlying SDK sent Authorization: Bearer <token> which the AWS API Gateway rejects on api.cryptohopper.com/v1/* (returns 405 Missing Authentication Token). The fix in @cryptohopper/sdk@0.4.0-alpha.2 switches to access-token: <token>. This PR picks up that fix and bumps the CLI to 0.6.0-alpha.2. No CLI surface change. Blocked on: cryptohopper/cryptohopper-node-sdk#9 (must merge and publish to npm before this CLI release can install the new SDK). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The Quickstart claimed 'cryptohopper ticker' worked without authentication. The auth-header fix in the underlying SDK (@cryptohopper/sdk@0.4.0-alpha.2, picked up by this PR's dep bump) establishes that EVERY endpoint requires a real token. The CLI inherits that — every subcommand including 'ticker' needs you to have run 'cryptohopper login' first.
Contributor
Author
|
Pushed a small follow-up commit ( |
The original PR bumped package.json's caret to ^0.4.0-alpha.2 but left the lockfile pinning the older 0.4.0-alpha.1, causing `npm ci` in CI to fail with EUSAGE (manifest/lockfile mismatch). Now that 0.4.0-alpha.2 is published to npm (it landed earlier today), `npm install` resolves the new version cleanly. Lockfile entry now records: node_modules/@cryptohopper/sdk: 0.4.0-alpha.2 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
pimfeltkamp
added a commit
that referenced
this pull request
Apr 28, 2026
The 0.6.0-alpha.2 entry only mentioned the auth-fix dep bump from #9. PRs #7 (cryptohopper upgrade version-comparison) and #8 (OAuth browser-flow state validation + token-exchange timeout) also landed on main without their own CHANGELOG lines. Folding all four bug fixes under the same release since none has shipped yet. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Why
The CLI consumes
@cryptohopper/sdkfor every API call. Until v0.4.0-alpha.2 of that SDK, the transport sentAuthorization: Bearer <token>which the AWS API Gateway in front ofapi.cryptohopper.com/v1/*rejects with405 Missing Authentication Token. That means every authenticated CLI command on 0.6.0-alpha.1 currently fails —cryptohopper whoami,cryptohopper hoppers list,cryptohopper backtest new, all of them.@cryptohopper/sdk@0.4.0-alpha.2(PR #9) switches toaccess-token: <token>, which is what the gateway expects. This CLI PR picks up that fix.Changes
package.json—@cryptohopper/sdkdep bumped from^0.4.0-alpha.1to^0.4.0-alpha.2. Note that npm's caret range is strict on pre-release versions:^0.4.0-alpha.1does NOT auto-resolve to0.4.0-alpha.2(different pre-release identifier), so the bump must be explicit.package.json+src/version.ts— CLI bumped to0.6.0-alpha.2.CHANGELOG.md— entry under "Fixed" with full root-cause writeup and an upgrade note.Compatibility
No CLI surface change. Same subcommands, flags, JSON output, exit codes. Only the wire-level header sent by the underlying SDK changes.
Test plan
npm run typecheckcleannpm run buildcleannpm install -g @cryptohopper/cli@0.6.0-alpha.2 && CRYPTOHOPPER_TOKEN=<real> cryptohopper whoamishould succeed where 0.6.0-alpha.1 returned an UNAUTHORIZED-looking error from the gateway.Blocked on
@cryptohopper/sdk@0.4.0-alpha.2must publish to npm before this PR'snpm installcan resolve the new dep. Do not merge until then.Companion releases also pending
The auth fix shipped to all 8 SDKs in parallel — see cryptohopper-resources#9 for the full PR list. The CLI is the last piece (it doesn't have its own transport — it consumes the Node SDK's).
Note on existing CLI 0.6.0-alpha.2 PRs
Two other fixes are sitting in the queue for the same release:
upgradeWhichever lands last will need a CHANGELOG merge to consolidate the three entries under one
0.6.0-alpha.2heading. Happy to do that after #7 and #8 merge if you'd like.