Documents

WAVit Documents

The written record of the WAVit Payments app lives in its repository — mostly as the release pipeline and its runbook. Paths are relative to the repository root.

Start here

Release Run templateMarkdownThe six-part checklist every production release follows: before you start, build and checks, go / no-go, approval, the manual upload to Clover, and verification. The pipeline renders it into a wiki page per release.release-run-template.md

READMEMarkdownFeature overview and team contacts. Last updated July 2025 and largely out of date — versions, SDK levels, hosts, dependencies and branching are all wrong. Prefer these pages.README.md

Release pipelines

Azure DevOps pipelines added in August 2026 (PRs 108 and 109). They build and sign; uploading to the Clover App Market is still manual.

Production pipelineYAMLRuns on a release/prod/v* tag (and builds PRs into master without publishing). Builds and signs the production APK, creates the Release Run wiki page, waits for approval on the clover-prod environment, then records the outcome.azure-pipelines.yml

Development pipelineYAMLBuilds and signs the development (Clover sandbox) APK on release/dev/v* tags or pushes to dev / staging. No approval gate, wiki page or Slack message.azure-pipelines-dev.yml

New-ReleaseRunPagePowerShellResolves the version from the tag, checks it matches productionVersionName and that the commit is on master, lists the changes since the previous prod tag and the linked work items, writes the wiki page and posts to Slack.scripts/New-ReleaseRunPage.ps1

Update-ReleaseRunPagePowerShellAppends the automated release record — result, approver, APK name, SHA-256, run link — once per build attempt, and posts the outcome to Slack.scripts/Update-ReleaseRunPage.ps1

Release Run pages

Each production release gets a page in the WAVit-Systems wiki at Releases-Run/WAVitPayments/{yyyy-MM-dd}-v{version}. It is the record of who approved what and when the APK went to Clover.