Skip to content

chore(deps): upgrade Cube.js + CubeStore 1.6.37 → 1.6.68#61

Merged
acmeguy merged 1 commit into
mainfrom
chore/cube-1.6.68-upgrade
Jul 7, 2026
Merged

chore(deps): upgrade Cube.js + CubeStore 1.6.37 → 1.6.68#61
acmeguy merged 1 commit into
mainfrom
chore/cube-1.6.68-upgrade

Conversation

@acmeguy

@acmeguy acmeguy commented Jul 7, 2026

Copy link
Copy Markdown

Upgrades all Cube.js libraries and CubeStore from 1.6.37 → 1.6.68 (latest), and fixes the reproducible-build gap that let Docker builds silently float.

Changes

  • cubejs: all 30 @cubejs-backend/*1.6.68
  • actions: @cubejs-client/core ^0.28.251.6.68
  • CubeStore: .env.example + docker-compose.stack.yml default → v1.6.68
  • Lockfiles: both yarn.lock regenerated to exact 1.6.68 (were stale at ^1.6.19)
  • Dockerfiles: added --frozen-lockfile — a stale lock now fails the build instead of re-resolving to the newest release

Why

Fixes the version-floating that broke builds (PR #59 pinned package.json but left the lock stale). Also picks up fixes that land directly on our feature surfaces: FILTER_PARAMS (1.6.61/65/66 — underpin 014 dynamic map/JSON), compiler-cache correctness (1.6.67 — 011/013), memberToAlias (1.6.63), ClickHouse custom HTTP headers (1.6.64), faster CubeStore repartition (1.6.61).

Tested locally (from-scratch frozen Docker builds)

  • actions unit 52/52, cubejs unit 613/615 (2 pre-existing buildWhereClause partition failures only — unchanged from 1.6.37)
  • SC-003 validator corpus 7/7prepareCompiler validation unchanged
  • All deep-internal imports (server-core/dist/..., api-gateway/dist/...) resolve with correct exports
  • Integration boot: /livez + /readyz = 200

Deploy note

The running dev CubeStore container is pinned (cubejs/cubestore:v1.6.37) in the infra repo and must be bumped to v1.6.68 alongside this merge so the store's partition format matches the driver.

🤖 Generated with Claude Code

Bump all 30 @cubejs-backend/* packages (cubejs) and @cubejs-client/core
(actions, 0.28.25 → 1.6.68) to the latest release, and align every
CubeStore reference (.env.example, docker-compose.stack.yml default) to
v1.6.68 so the store's partition format matches the driver.

Reproducible-build hardening:
- Regenerate both yarn.lock files to exact 1.6.68 (were stale at ^1.6.19,
  which let the Docker build silently float to whatever was newest).
- Add --frozen-lockfile to both Dockerfiles so a stale lock now fails the
  build instead of re-resolving.

Benefits picked up from 1.6.38–1.6.68: FILTER_PARAMS fixes (1.6.61/65/66,
underpin the 014 dynamic map/JSON rewrite), compiler-cache correctness fix
(1.6.67, used by 011/013), memberToAlias threading (1.6.63), ClickHouse
custom HTTP headers (1.6.64), faster CubeStore repartition (1.6.61).

Tested locally (from-scratch frozen builds): actions 52/52, cubejs 613/615
(2 pre-existing buildWhereClause partition failures only, unchanged from
1.6.37), SC-003 validator corpus 7/7, all deep-internal imports resolve,
service boots with /livez + /readyz = 200.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@acmeguy acmeguy merged commit 0704211 into main Jul 7, 2026
3 checks passed
@acmeguy acmeguy deleted the chore/cube-1.6.68-upgrade branch July 7, 2026 17:56
acmeguy added a commit that referenced this pull request Jul 7, 2026
…core 1.x (#62)

The 1.6.68 client (#61) renamed the API class CubejsApi → CubeApi and
switched to ESM named exports, so `const { CubejsApi } = cubejsClientCore`
resolved to undefined and `new CubejsApiClient(...)` threw
"CubejsApiClient is not a constructor" — breaking every run_query /
run_sql path through the actions service (client-v2 GraphQL errors).

Import the class by its new name via a named import; constructor
signature and .meta()/.sql()/.load() are unchanged. Verified in a
1.6.68 image: constructor + methods present, cubejsApi.js loads clean.

Missed by unit tests because they never construct the client at runtime.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant