Skip to content

ContextGate 0.7.0 — Cloud warehouse previews

Choose a tag to compare

View all tags
@SamuelSupe SamuelSupe released this 15 Sep 13:01
· 2 commits to main since this release
v0.7.0
89cf20d

ContextGate 0.7.0

Cloud warehouse previews for the same semantic data workflow.

简体中文 · Cloud warehouse guide · Examples · Installation

What's new

Snowflake, Databricks SQL, Google BigQuery and Amazon Redshift join ContextGate as preview connectors. They use the existing query_sql tool, Agent-to-source grants, semantic catalogs, verified native templates, ontology mappings, and audit/OTLP pipeline. Configuration is available in the English/Chinese UI and Configuration MCP.

Connector Access and query interface Parameters
Snowflake SQL API with PAT or preissued OAuth access token Positional ?
Databricks SQL Statement Execution API with PAT or preissued OAuth access token Named :name
Google BigQuery Jobs API with Google service account JSON and automatic token refresh, or a supplied access token Named @name
Amazon Redshift PostgreSQL protocol with username/password, TLS and per-query read-only transactions Positional $1

The three HTTPS adapters use fixed API paths, verified TLS, bounded polling and native result pages, and best-effort remote cancellation. BigQuery performs a dry run requiring a SELECT statement and applies a configurable billed-byte limit. Source discovery, credential editing and reader-declaration evidence follow the existing configuration workflow. Each connector includes source JSON and an importable semantic-template example.

Preview boundaries

No real Snowflake, Databricks, BigQuery or Redshift environment has been verified. These connectors are included in the packages, but are excluded from the verified 18-product / 20-version database count. API fixtures establish local behavior, not vendor compatibility, grants, billing or production readiness.

Cloud SQL accepts a conservative SELECT subset. Advanced vendor syntax can be rejected; native parameters are scalar, and SQL pagination is explicit. Use dedicated reader principals. A successful connection or administrator reader declaration is not proof of account privileges. See the guide for exact authentication, discovery, types, cancellation and cost boundaries.

HTTPS source versions are manually maintained connection-contract versions. Update the version after relevant cloud contract changes, then trial and publish affected templates again. This release does not add cross-source queries, a unified SQL compiler or entity-result conversion.

Upgrade

From 0.6.x, back up the PostgreSQL metadata database, matching master key and deployment configuration. Stop the service, replace the package or image with 0.7.0, then start with the same database URL, key and data directories. This release introduces no new metadata migration or forced credential rotation. Existing administrator accounts, personal Configuration MCP identities, query Agent/OAuth grants, semantic publications and ontology mappings remain in place. Check a known query and its audit record after restarting.

From 0.4.x or 0.5.x, the administrator migration introduced in 0.6.0 still applies: sign in as admin with the retained password, and replace revoked legacy Configuration MCP tokens with personal tokens. Follow the account upgrade checklist. From 0.3.x or earlier, follow the PostgreSQL storage migration guidance.

Packages and verification

Download contextgate-0.7.0-linux-arm64.tar.gz or contextgate-0.7.0-linux-amd64.tar.gz with SHA256SUMS. Both include the embedded UI, private C++ runtime libraries, English/Chinese help, cloud examples, Apache-2.0 LICENSE/NOTICE and dependency notices. Linux glibc 2.36+ and PostgreSQL metadata are required; Node.js is not needed at runtime.

Release attachments record the exact commit, native arm64/amd64 CI, and checks on both built archives and independent GitHub downloads. Archive workflows exercise PostgreSQL and HTTP API queries, HTTP/stdio, semantic/ontology templates, administrator access, recovery and both OTLP transports. Local amd64 archive execution uses OrbStack emulation. The validation record separates the open-source database matrix, local Chrome checks and simulated cloud API tests from the remaining real-cloud validation gap.

Downloads

Verified release gates

  • Native amd64 and arm64 CI: Go, race, UI tests, production UI and CLI builds passed.
  • Open-source database matrix: 18 products / 20 versions, 135 query/error cases and 104 denied operations passed.
  • Each architecture passed 54 archive checks and another 54 checks after an independent GitHub download, including HTTP/stdio, semantic/ontology templates, administrator recovery and OTLP HTTP/gRPC.
  • Archive hashes and source commit 89cf20d7c55a145f22c29e2019a792a858711af4 match. Four cloud connectors remain Preview; no real vendor environment was verified.
Assets 12
Loading