Repository navigation
Comparing changes
Open a pull request
base repository: stackql/stackql-assert
base: 72d1189
head repository: stackql/stackql-assert
compare: e55b801
- 15 commits
- 15 files changed
- 3 contributors
Commits on Apr 28, 2024
-
Merge pull request #23 from stackql/feature/updates
use stackql-exec
Configuration menu - View commit details
-
Copy full SHA for a6155a6 - Browse repository at this point
Copy the full SHA a6155a6View commit details
Commits on Oct 28, 2024
-
Configuration menu - View commit details
-
Copy full SHA for e13ecc4 - Browse repository at this point
Copy the full SHA e13ecc4View commit details
Commits on Oct 29, 2024
-
Configuration menu - View commit details
-
Copy full SHA for e3c02b2 - Browse repository at this point
Copy the full SHA e3c02b2View commit details
Commits on Mar 14, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 6dfcf6f - Browse repository at this point
Copy the full SHA 6dfcf6fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 18f75a2 - Browse repository at this point
Copy the full SHA 18f75a2View commit details -
Replace Google Compute instance tests with stable GCS bucket resource
Switch all Google test references from google.compute.instances (stackql-integration-tests project, australia-southeast1-a zone) to google.storage.buckets (stackql project, stackql-public-releases bucket). Bucket properties (name, location, locationType) are stable and not subject to instance lifecycle costs. Remove GOOGLE_ZONE variable dependency throughout. https://claude.ai/code/session_019CH6RrcMGtdUafvyVCKCHE
Configuration menu - View commit details
-
Copy full SHA for 101b276 - Browse repository at this point
Copy the full SHA 101b276View commit details -
Fix expected result key ordering to match stackql JSON output
stackql serialises JSON keys alphabetically, so expected result strings must use the same order (location, locationType, name) to pass deep equality checks. https://claude.ai/code/session_019CH6RrcMGtdUafvyVCKCHE
Configuration menu - View commit details
-
Copy full SHA for 6b2050a - Browse repository at this point
Copy the full SHA 6b2050aView commit details -
Fix key-order-sensitive comparison and hardcode stable project var
assert.js: replace JSON.stringify deep equality with key-sorted comparison so JSON objects match regardless of key order. stackql-assert-test.yml: hardcode GOOGLE_PROJECT=stackql in the inline jsonnet test vars instead of pulling from the repo variable (which still pointed at stackql-integration-tests). https://claude.ai/code/session_019CH6RrcMGtdUafvyVCKCHE
Configuration menu - View commit details
-
Copy full SHA for 192918b - Browse repository at this point
Copy the full SHA 192918bView commit details
Commits on Mar 15, 2026
-
Merge pull request #26 from stackql/claude/update-google-test-locatio…
…ns-AE07x Replace Google Compute instance tests with stable GCS bucket resource
Configuration menu - View commit details
-
Copy full SHA for 61a59c1 - Browse repository at this point
Copy the full SHA 61a59c1View commit details
Commits on Jul 20, 2026
-
Remove redundant unconditional setup-stackql step
stackql-assert ran setup-stackql on every invocation and then called stackql-exec, which already performs a guarded, reuse-if-present install. The extra setup step re-downloaded the binary each time, and when it ran after a workflow flipped the releases "latest" pointer it could 404. Drop the redundant step; setup is handled by stackql-exec. The Check Results step needs no stackql binary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for cf5b39e - Browse repository at this point
Copy the full SHA cf5b39eView commit details -
Handle empty (null) query result without crashing
stackql emits the literal `null` for a query that matches no rows. assertResult parsed that to null and then read `.length` on it, throwing "Cannot read properties of null (reading 'length')" instead of reporting a clean assertion failure. Normalise a non-array parsed result to an empty array so a 0-rows-vs-expected case fails with a readable message. Adds coverage. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 5a91a98 - Browse repository at this point
Copy the full SHA 5a91a98View commit details -
Point google tests at project resource instead of deleted bucket
The gcs bucket stackql-public-releases used by the google test steps no longer exists, so the queries returned no rows and the tests failed. Switch them to google.cloudresourcemanager.projects (projectsId = 'stackql'), a stable resource, asserting projectId/displayName/state. Values verified live: projectId=stackql, displayName=stackql, state=ACTIVE. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 61a3e35 - Browse repository at this point
Copy the full SHA 61a3e35View commit details
Commits on Oct 12, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 07545e0 - Browse repository at this point
Copy the full SHA 07545e0View commit details
Commits on Oct 13, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 5c500a1 - Browse repository at this point
Copy the full SHA 5c500a1View commit details
Commits on Oct 22, 2026
-
Move to github-script v9, checkout v7 and setup-node v7
- actions/github-script v9 in action.yml - actions/checkout v7 and actions/setup-node v7 with check-latest in CI (October 2026 Node.js security releases) - CONTRIBUTING: Node.js 24.22.1 or later Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for e55b801 - Browse repository at this point
Copy the full SHA e55b801View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 72d1189...e55b801