-
Notifications
You must be signed in to change notification settings - Fork 0
background
Douwe de Vries edited this page Jul 1, 2026
·
2 revisions
This section gives maintainer context behind the current architecture, release automation, and known tradeoffs. Start with release history, then read pitfalls before changing persistence, transport, packaging, or comparison behavior.
| Page | What it covers |
|---|---|
| Release history | How the release line evolved, why packaging automation exists, and which release-era changes still affect maintenance. |
| Pitfalls | Known failure modes and design tradeoffs around transports, sessions, flexible keys, saved files, and packaging. |
- Overview explains the main runtime architecture.
- Contributor guide defines the normal development and validation expectations.
- Deployment describes CI, release assets, Linux packages, APT repository publishing, and macOS DMGs.
- Cleanup opportunities captures current complexity hotspots and dependency watch areas.
| File | Purpose |
|---|---|
/Users/vriesd/projects/csv-align/CHANGELOG.md |
Release chronology and behavior changes. |
/Users/vriesd/projects/csv-align/docs/releasing.md |
Maintainer release process and signing background. |
/Users/vriesd/projects/csv-align/.github/workflows/ci.yml |
CI evolution and current validation gates. |
/Users/vriesd/projects/csv-align/.github/workflows/release.yml |
Tagged release automation. |
/Users/vriesd/projects/csv-align/src/backend/persistence/v1/mod.rs |
Current saved comparison snapshot schema. |