Skip to content

index.md

Latest commit

 

History

History
70 lines (52 loc) · 1.79 KB

index.md

File metadata and controls

70 lines (52 loc) · 1.79 KB
Raw

Operations and Release Checklist

日本語

Use this checklist before publishing AIKernel.Wasm packages.

Build and Test

dotnet build AIKernel.Wasm.slnx -c Release -p:WarningsAsErrors=1591
dotnet test AIKernel.Wasm.slnx -c Release --no-build

Success criteria:

  • no XML documentation warnings for public C# members
  • all runtime tests pass
  • all audio, display, input, and concept-elevation boundary tests pass
  • all WebGPU provider tests pass

Package Metadata

Check NuGet package metadata:

  • package ID
  • version
  • license expression
  • project URL
  • repository URL
  • package icon
  • README inclusion
  • release notes

For the v0.1.2.1 NuGet patch, publish AIKernel.Wasm package artifacts as 0.1.2.1 while keeping AIKernel.NET, AIKernel.Core, and AIKernel.Providers dependencies on 0.1.2. Validate the aikernel-wasm wheel with 0.1.2.dev{buildNumber} unless a separate PyPI patch task explicitly requests a Python wrapper update.

Documentation

Required documentation:

  • repository README in English and Japanese
  • docs index in English and Japanese
  • architecture guide
  • runtime provider guide
  • browser boundary provider guide for audio, display, and input
  • WebGPU guide
  • concept elevation notes
  • Python wrapper reference guide
  • testing guide
  • licensing guide
  • manifest and metadata guide

Browser GPU Validation

Automated Release tests do not require a physical GPU. Browser WebGPU validation should be tracked separately as E2E validation because it depends on browser, driver, adapter, and platform state.

Safety Checks

Before release, scan docs and reference Python sources for:

  • stale capability IDs
  • temporary or incomplete wording
  • unsafe scheduler examples
  • sensitive metadata
  • browser implementation objects leaking into public descriptors