Repository navigation
Release ndc-jvm MySQL v1.0.21, Snowflake v1.2.1, Oracle v1.2.5, Trino v1.0.7 - #776
Merged
Merged
Conversation
GavinRay97
approved these changes
Nov 18, 2026
…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.
This branch was successfully deployed
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
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.
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:hasura/mysqlghcr.io/hasura/ndc-jvm-mysql:v1.0.21ghcr.io/hasura/ndc-jvm-cli:v1.0.21-mysqlhasura/snowflakeghcr.io/hasura/ndc-jvm-snowflake:v1.2.1ghcr.io/hasura/ndc-jvm-cli:v1.2.1-snowflakehasura/oracleghcr.io/hasura/ndc-jvm-oracle:v1.2.5ghcr.io/hasura/ndc-jvm-cli:v1.2.5-oraclehasura/trinoghcr.io/hasura/ndc-jvm-trino:v1.0.7ghcr.io/hasura/ndc-jvm-cli:v1.0.7-trinoEach
connector-packaging.jsonpoints at the<db>-connector-v<ver>.tar.gzasset on the matching GitHub Release; the sha256 values were computed from the downloaded assets and re-checked against the URIs.source.hashis 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-headlesswith all RHEL errata, dependency bumps to clear HIGH/CRITICAL CVEs, the emSign Root CA - G1 distrust, andJDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsicsas 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,
/healthand/capabilities200. The Snowflake image was also queried live against the CI Snowflake account (schema validation, ndc-test replay, hand-written queries).