-
Notifications
You must be signed in to change notification settings - Fork 0
deployment
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
QA Scribe deploys as desktop release artifacts through GitHub Releases and a signed Linux APT repository. The release process is encoded in GitHub Actions and helper scripts.
| File | Purpose |
|---|---|
.github/workflows/release.yml |
Release workflow for desktop artifacts and package repository outputs. |
.github/workflows/ci.yml |
Verification workflow. |
docs/releasing.md |
Human release runbook. |
scripts/package-tauri-linux.mjs |
Linux artifact packaging. |
scripts/package-rust-macos.mjs |
macOS artifact packaging. |
scripts/build_apt_repository.py |
APT repository generation. |
scripts/install-apt-repo.sh |
User-facing APT setup script. |
scripts/check-release-metadata.mjs |
Release metadata validation. |
package.json defines release:check, linux:metadata:check, linux:metadata:test, apt:repo:check, and apt:installer:check. README.md documents the install path for macOS, Linux package files, and the APT bootstrap.
Release tooling depends on Tooling, Release tooling, and Reference configuration.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies