Repository navigation
ARCS v1.1.0 — Release Notes (First non‑beta)
Release date: 2025-12-28
🚀 Highlights
- First non-beta release — stability and user-facing polish improvements.
- New PDF export options: export quotes as
- Purchasing (Unit Cost) — procurement-ready parts lists.
- Customer (List Price) — retail/quote for customers.
- Both — generate both files at once. (UI: Export dialog; internal helper
_generate_pdfadded.) ✅
🛠 Improvements & Fixes
-
Export & UI
- Added dialog to select export type (Purchasing / Customer / Both).
- PDFs clearly label which mode they represent and compute line totals from the chosen price field (
unit_costorlist_price). - Filenames default to friendly, suffixed names:
*_purchasing.pdfand*_customer.pdf.
-
Build / Distribution
buildtools/macOSBuildnow cleans staledist/buildartifacts and runs PyInstaller with--cleanto avoid stale-artifact failures.data/ARCS.specadjusted to avoid EXE/collect name collisions (internal EXE renamed toARCS_bin), preventing a build-time ValueError.- Note: macOS codesign may still warn about extended attributes — instructions included below to clear them before signing.
-
Data & Behavior
- Margin calculation and supplier tax-exempt mapping improvements maintained and clarified.
- PDF generation computes totals on-the-fly (no mutation of stored quote
line_total), avoiding surprises.
📝 Upgrade / Compatibility Notes
- No data migrations required — quotes created with prior versions remain compatible.
- If you build on macOS, consider clearing extended attributes and signing the app if you need an App Store / notarized package:
- Clear extended attributes:
xattr -cr dist/ARCS.app - Sign example:
codesign -s "<Your Identity>" --options runtime --deep dist/ARCS.app
- Clear extended attributes:
✅ How to build locally
- Clean + build on macOS:
./buildtools/macOSBuild
- Built artifacts are in
dist/(ARCS.app,ARCS_bin, andARCSfolder as applicable).
🐞 Known issues
- Codesign may emit a warning about resource forks on some files — use
xattr -crto clear them before signing (see Upgrade notes).
🙏 Credits & Thanks
- Thanks to the team and contributors for testing and feedback. If you find issues or want enhancements, please open an issue or PR with reproduction steps.