Skip to content

Release ndc-jvm MySQL v1.0.21, Snowflake v1.2.1, Oracle v1.2.5, Trino v1.0.7 - #776

Merged
codedmart merged 2 commits into
mainfrom
brandon/ndc-jvm-releases-2026-11-18
Nov 19, 2026
Merged

codedmart merged 2 commits into
mainfrom
brandon/ndc-jvm-releases-2026-11-18

Conversation

@codedmart

Copy link
Copy Markdown
Contributor

Adds the ndc-jvm-mono releases cut from hasura/ndc-jvm-mono@7606ff9 (merge of ndc-jvm-mono#103) and bumps each connector's latest_version:

Connector Version Connector image CLI image
hasura/mysql v1.0.21 ghcr.io/hasura/ndc-jvm-mysql:v1.0.21 ghcr.io/hasura/ndc-jvm-cli:v1.0.21-mysql
hasura/snowflake v1.2.1 ghcr.io/hasura/ndc-jvm-snowflake:v1.2.1 ghcr.io/hasura/ndc-jvm-cli:v1.2.1-snowflake
hasura/oracle v1.2.5 ghcr.io/hasura/ndc-jvm-oracle:v1.2.5 ghcr.io/hasura/ndc-jvm-cli:v1.2.5-oracle
hasura/trino v1.0.7 ghcr.io/hasura/ndc-jvm-trino:v1.0.7 ghcr.io/hasura/ndc-jvm-cli:v1.0.7-trino

Each connector-packaging.json points at the <db>-connector-v<ver>.tar.gz asset on the matching GitHub Release; the sha256 values were computed from the downloaded assets and re-checked against the URIs. source.hash is 7606ff9 for all four.

What changed in these releases (ndc-jvm-mono#103): security update. Runtime images move to ubi9/ubi-minimal:9.9 + java-21-openjdk-headless with all RHEL errata, dependency bumps to clear HIGH/CRITICAL CVEs, the emSign Root CA - G1 distrust, and JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics as Red Hat's temporary mitigation for Java4Shell (CVE-2026-114938) until a fixed JDK RPM ships.

Verification: all 8 images (amd64 + arm64) were pulled from ghcr and checked: provenance revision 7606ff9, uid 185, mitigation flag active in the JVM, /health and /capabilities 200. The Snowflake image was also queried live against the CI Snowflake account (schema validation, ndc-test replay, hand-written queries).

@codedmart
codedmart marked this pull request as ready for review November 18, 2026 23:21
…fail on login errors

The workspace container received both HASURA_DDN_PAT and DDN_WORKSPACE_ACCESS_TOKEN, so
`ddn auth login --access-token` always failed with "Only one of --pat, --access-token, ...
can be used". The failure was swallowed, which was harmless until `ddn supergraph init`
started requiring a session ("Unable to retrieve engine files: Invalid user session").

Prefer the staging access token (the workspace runs the staging CLI) and only fall back to
HASURA_DDN_PAT when it is absent; a failed login now fails the test instead of continuing.
@codedmart
codedmart deleted the brandon/ndc-jvm-releases-2026-11-18 branch November 19, 2026 02:03

This branch was successfully deployed

1 active deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants