Repository navigation
AirPDF 0.2.1
A packaging release. The application binaries are unchanged from 0.2.0; this version ships the signing tooling and makes the release pipeline state explicit.
Downloads
| Platform | Package |
|---|---|
| Windows x64 | AirPDF-win-Portable.zip — unzip and run AirPdf.exe |
| macOS Apple Silicon | Portable zip — unzip and drag the app to Applications |
| macOS Intel | Portable zip — unzip and drag the app to Applications |
| Linux x64 | AirPDF-0.2.1-linux-x64.tar.gz |
The installers were withdrawn on 3 November 2026: these builds are unsigned, and SmartScreen and Gatekeeper block an unsigned first launch, which reads as a fault in the reader. The portable packages above are the same build. The first launch may need More info → Run anyway on Windows, or right-click → Open on macOS.
Installed Windows and macOS builds update themselves: they check this release channel, download in the background, and offer Restart to update. Portable and source builds do not self-update.
What changed
packaging/signing/Set-SigningSecrets.ps1validates a code-signing certificate (private key, Code Signing extended key usage, expiry) and uploads it as the repository secrets the release workflow consumes.packaging/signing/New-TestCertificate.ps1mints a throwaway certificate so the signing path can be exercised without a purchased one.- A Signing check workflow verifies the configured credentials without publishing anything.
- The release workflow now fails when signing is half configured instead of silently shipping an unsigned build, and states the signing outcome in the run summary.
docs/SIGNING.mddocuments certificate acquisition, secret names, verification, rotation, and cost.
The reading experience is unchanged: packages still bring PDFium rendering, search, text selection, reading position memory, tabs, multiple windows, links, and English/Simplified Chinese.
Code signing status
These builds are unsigned. No Windows or Apple signing credentials are configured in this repository yet, so:
- Windows SmartScreen will warn about an unknown publisher until the file builds reputation.
- macOS Gatekeeper blocks the
.pkg/.appon other machines. Right-click → Open, orxattr -dr com.apple.quarantineon the app, works around it locally.
The pipeline is ready and verified; see docs/SIGNING.md to add credentials.
Verification
- Core and headless UI tests: 52/52 passing
- CI: Windows, Ubuntu, and macOS green
- Release workflow: all four platform packages built and attached, including the
releases.*.jsonmanifests the in-app updater reads - Signing check: passes with a throwaway certificate, confirming the signing path works end to end
Full changelog: CHANGELOG.md