Eve library

Neith Release Training Materials

Guide

Revision 1

On this page

Training path for engineers and operators onboarding to @neith/release.

Audience#

  • release engineers building new automation
  • QA or operations staff validating release gates
  • platform owners publishing to desktop, mobile, web, or marketplace targets

Learning Objectives#

  • design release pipelines, version plans, and rollout controls that match the implemented release package
  • publish distribution artifacts with verifiable integrity and recovery paths
  • exercise platform publication workflows across desktop, mobile, web, Docker, and marketplace targets
  • produce the benchmark, accessibility, and release evidence expected by Phase 52 quality gates

Prerequisites#

  • TypeScript familiarity
  • basic semantic versioning knowledge
  • working repository checkout with pnpm install

Learning Path#

Module 1: Release Foundations#

Goal: understand branching, versioning, and release-pipeline composition.

Exercises:

  1. Parse and compare semantic versions.
  2. Generate a release branch and hotfix branch.
  3. Build a stable release workflow with security and publish stages.

Module 2: Controlled Rollouts#

Goal: practice RC promotion, beta programs, early access, staged rollout, and rollback planning.

Exercises:

  1. Create an RC and evaluate promotion gates.
  2. Enroll a beta cohort and capture sample feedback.
  3. Configure ring-based rollout thresholds and simulate rollback decisions.

Module 3: Distribution Operations#

Goal: publish artifacts, integrity evidence, and installation metadata.

Exercises:

  1. Register artifacts in the download infrastructure.
  2. Generate checksums and signature records.
  3. Build offline installers and package-repository outputs.
  4. Resolve an auto-update decision and evaluate delta savings.

Module 4: Platform And Quality Gates#

Goal: exercise platform publication, accessibility, and performance validation.

Exercises:

  1. Materialize Linux, Windows, macOS, Docker, and marketplace artifacts.
  2. Audit a web distribution manifest for WCAG 2.1 AA minimum compliance.
  3. Run the benchmark suite and interpret both the budget and regression reports.

Hands-On Labs#

  1. Assemble a stable release train from version planning through publish-stage automation.
  2. Rehearse an RC-to-staged-rollout promotion and a rollback decision using the same release metadata.
  3. Produce a verified distribution bundle containing checksums, signatures, offline installers, and auto-update metadata.
  4. Publish target-specific output for one desktop channel, one mobile/store channel, one web channel, and one marketplace channel.
  5. Capture benchmark and accessibility evidence suitable for signoff.

Suggested Workshop Sequence#

Workshop Duration Outcome
Release authoring 90 min engineers can create pipelines and version plans
Safe rollout operations 90 min operators can pause, advance, or roll back safely
Distribution and publishing 120 min platform teams can produce target-specific artifacts
Evidence and signoff 60 min QA can produce benchmark and accessibility evidence

Assessment And Evidence#

Successful completion means the trainee can:

  • explain how a release moves from version planning to controlled rollout
  • generate distribution evidence that supports download integrity and recovery
  • identify which tests or certification ledgers need to move when release behavior changes
  • produce enough benchmark and accessibility evidence for a signoff package

Commands Used In Training#

bash
pnpm nx run @neith/release:typecheck
pnpm nx run @neith/release:lint
pnpm nx run @neith/release:test
pnpm nx run @neith/release:integration
pnpm nx run @neith/release:e2e
pnpm nx run @neith/release:benchmark

Review libs/neith/release/tests/*.spec.ts alongside these materials. The test suite doubles as executable training examples for most workflows.