GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Comparing v2.3.1...v2.4.0 · stackql/stackql-assert

Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: stackql/stackql-assert
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading

Uh oh!

There was an error while loading. Please reload this page.

base: v2.3.1
Loading
Loading
...
head repository: stackql/stackql-assert
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading

Uh oh!

There was an error while loading. Please reload this page.

compare: v2.4.0
Loading
Loading
  • 3 commits
  • 7 files changed
  • 2 contributors

Commits on Jul 20, 2026

  1. 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) <[email protected]>
    @jeffreyaven @claude
    jeffreyaven and claude committed Jul 20, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for cf5b39e
    • Browse repository at this point
    Copy the full SHA
    cf5b39e View commit details
    Browse the repository at this point in the history
  2. 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) <[email protected]>
    @jeffreyaven @claude
    jeffreyaven and claude committed Jul 20, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for 5a91a98
    • Browse repository at this point
    Copy the full SHA
    5a91a98 View commit details
    Browse the repository at this point in the history
  3. 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) <[email protected]>
    @jeffreyaven @claude
    jeffreyaven and claude committed Jul 20, 2026
    Configuration menu
    • View commit details
    • Copy full SHA for 61a3e35
    • Browse repository at this point
    Copy the full SHA
    61a3e35 View commit details
    Browse the repository at this point in the history
Loading

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 v2.3.1...v2.4.0

Uh oh!

There was an error while loading. Please reload this page.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.