Skip to content

server-info-and-pinned-installers - #936

Merged
jeffreyaven merged 1 commit into
mainfrom
feature/pinned-release-installers-930-931
Nov 18, 2026
Merged

jeffreyaven merged 1 commit into
mainfrom
feature/pinned-release-installers-930-931

Conversation

@jeffreyaven

Copy link
Copy Markdown
Member

Description

Correct the server_info guidance in the MCP documentation to match the server instructions, including the missing mode field in the MCP README table. Add optional release-version pinning to the get-stackql.io Worker through a query parameter or leading path segment. Accept v-prefixed versions, preserve latest behavior, reject invalid values without reflecting them, and report missing platform assets with a release link. Update the get-app README and both installer smoke tests.

Type of change

  • Bug fix (non-breaking change to fix a bug).
  • Feature (non-breaking change to add functionality).
  • Breaking change.
  • Other (eg: documentation change). Please explain.

Issues referenced.

Evidence

  • cd get-app; node node_modules\typescript\bin\tsc --noEmit --target es2022 --module esnext --moduleResolution bundler --strict --lib es2022 --types @cloudflare/workers-types src\index.ts src\cloud-shell-scripts.ts: passed.
  • sh -n get-app/test-get-app.sh: passed.
  • PowerShell parser check for get-app/test-get-app.ps1: passed.
  • TypeScript-compiled Worker fetch assertions: passed for latest behavior, query and path pins, provider routes, invalid query/path values, and pinned root redirects.
  • Generated sh and PowerShell installers were exercised with simulated missing-asset responses: both emitted the asset-specific message and version release link.

Checklist:

  • A full round of testing has been completed, and there are no test failures as a result of these changes.
  • The changes are covered with functional and/or integration robot testing.
  • The changes work on all supported platforms.
  • Unit tests pass locally, as per the developer guide.
  • Robot tests pass locally, as per the developer guide.
  • Linter passes locally, as per the developer guide.

Variations

The full Go, Robot, and lint suites were not run because this change does not affect StackQL query behavior. The live installer smoke tests were not run because the Worker changes are not deployed. npm --prefix get-app run dev -- --local --ip 127.0.0.1 --port 8787 could not start: the existing workerd installation contains the Linux binary, while this host is Windows. The Worker was instead compiled and its fetch handler and generated installer failure flows were exercised directly.

Tech Debt

No technical debt introduced.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jeffreyaven jeffreyaven changed the title pinned-release-installers server-info-and-pinned-installers Nov 18, 2026
@jeffreyaven
jeffreyaven merged commit 256187f into main Nov 18, 2026
9 checks passed
@jeffreyaven
jeffreyaven deleted the feature/pinned-release-installers-930-931 branch November 18, 2026 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant