Releases
v1.0.2
Windows and MacOS executables v1.0.2
Latest
Compare
Sorry, something went wrong.
No results found
Changelog
1.0.2
Added
Added macOS command-line executable distribution for Marketplace review and customer-run testing.
Added Apple Silicon and Intel macOS build artifacts:
release-notes-sync-macos-arm64.zip
release-notes-sync-macos-intel.zip
Added macOS PyInstaller workflow to build onefile CLI executables for both project modes:
release-notes-sync-jpd-macos
release-notes-sync-jira-software-macos
Added ad-hoc macOS code signing during the build workflow.
Added workflow support for uploading tested macOS ZIP files directly to an existing GitHub Release by providing release_tag.
Added macOS direct execution guides in English and Portuguese:
README_DIRECT_EXECUTION_MACOS.md
README_DIRECT_EXECUTION_MACOS.pt-BR.md
Added macOS executable testing guide for Marketplace reviewers:
Added macOS packaging and release workflow documentation:
Changed
Updated the main English and Portuguese READMEs to point to the Windows and macOS execution guides.
Kept Windows direct execution documentation separate from macOS direct execution documentation.
Updated the Windows testing guide to point reviewers to the dedicated macOS testing guide.
Clarified that macOS builds are command-line executables, not .app bundles.
Clarified architecture selection for macOS downloads:
arm64 for Apple Silicon Macs
x86_64 for Intel Macs
Documentation
Documented macOS Gatekeeper and quarantine troubleshooting with:
xattr -dr com.apple.quarantine .
chmod +x ./release-notes-sync-jpd-macos ./release-notes-sync-jira-software-macos
Documented how reviewers should download macOS ZIP files from GitHub Releases and run configure, validate-config, dry-run, and optional sync.
Moved maintainer-only build and release flow details out of the reviewer testing guide and into docs/PACKAGING_MACOS.md.
Security and privacy
Jira API tokens and Atlassian Admin cookies remain runtime-only.
macOS packaging does not add credential storage or any hosted backend.
The local configuration file still stores only project settings, field mappings, source preferences, and validated Jira field schema.
You can’t perform that action at this time.