Skip to content

SQL Apps 0.2.4 - runtime archive release

Latest
Latest

Choose a tag to compare

View all tags
@itsnotaboutthecell itsnotaboutthecell released this 20 Oct 21:18
v0.2.4
09cad66

Highlights

  • Clarify free-first cloud planning: assess compatible App Service Free hosting first, Container Apps for required DAB/container workloads next, and a fully qualifying Static Web Apps Free fallback last. Preserve existing personal-free deployments and require explicit cost-risk approval.
  • Harden personal-free artifact builds, deployment validation, temporary SQL publishing access, and end-to-end workflow checks.
  • Verify SQL readiness through the declared readiness procedure and check DAB readiness at its root endpoint without following redirects.
  • Verify pooled SQL identity isolation, session-context cleanup, error recovery, and aborted-transaction handling against the real Azure SQL Database engine.
  • Align the runtime package, assistant plugin manifests, marketplace metadata, documentation, and fixtures at 0.2.4.

Installable runtime archive

This release supplies the exact @microsoft/sql-apps@0.2.4 runtime as a versioned archive. It is a GitHub archive release, not an npm publication, and does not require Microsoft npm organization membership.

  1. Download microsoft-sql-apps-0.2.4.tgz and SHA256SUMS, and verify the archive SHA-256 against the checksum.
  2. Update the foundation checkout to this release and review the archive binding plan:
npm run tooling:bind -- --project "C:\SqlAppsProjects\my-app" --archive "C:\Downloads\microsoft-sql-apps-0.2.4.tgz"
  1. Review the version, checksum, destination, and effects, then repeat with --approve <approval-id>.
  2. Review a new setup plan and approve the intended restore before building or starting the application.

Keep the copied archive and lockfile with the application. Other dependencies still use the configured npm registry; there is no silent registry fallback.

Archive installation reference

Validation

Local validation on Windows with Node.js 22.22.2:

  • npm test: passed, 603 tests passed and 2 Windows symlink-permission tests skipped.
  • npm run test:sql-integration: passed, all 4 real Azure SQL Database integration tests, including pooled identity isolation and concurrent Todo limits.
  • npm run infra:test: passed, 1 test.
  • npm run typecheck: passed.
  • npm run plugin:check: passed.
  • npm run tooling:build: passed.
  • npm run tooling:check: passed.
  • npm run tooling:verify-archive -- C:\git\sql-apps\dist\microsoft-sql-apps-0.2.4.tgz: passed, independent generated-project restore with an empty npm cache and packaged CLI startup.

The attached archive and checksum are from the successful runtime packaging workflow, pinned to commit 09cad667b7ab405deeba7b4b90ffe1b545b720e0. That workflow runs the full test suite, validates package inventory, and independently verifies archive restoration with an empty cache before calculating the checksum.

The Azure-native validation workflow also passed: all 12 jobs, including Windows/Linux validation on Node.js 22 and 24, native Claude/Copilot plugin loading, and Windows/Linux/macOS setup diagnostics. The validation matrix includes npm test, npm run typecheck, npm run dab:validate, npm run sql:tools, npm run sql:build, SQL model validation, npm run infra:build, and npm run infra:test.

Real SQL integration results establish local engine behavior, not live Azure deployment acceptance. Archive restoration verifies installation and CLI startup, not a running application or rendered-design acceptance.

Assets 4
Loading