Releases: SagaHealthcareIT/mirthsync
3.5.0
3.5.0-SNAPSHOT
- Bulk Channel Deployment: New --deploy-all flag for efficient bulk deployment of multiple channels
- Deploys all channels in a single operation instead of one-by-one
- Significantly faster when pushing multiple channels
- Allows Mirth's dependency logic to control deployment order
3.4.0-SNAPSHOT
Key Changes in 3.4.0-SNAPSHOT
- Windows CI support: GitHub Actions now tests on both Ubuntu and Windows runners
- Cross-platform utilities: Replaced Unix-specific commands with Java-based implementations
- Fixed a few minor potential Windows issues with the changes included in 3.2.0-SNAPSHOT and 3.3.0-SNAPSHOT
3.3.0-SNAPSHOT
SNAPSHOT Release
This release contains new features that are still being tested. Use with caution in production environments.
What's New
Enhanced Orphaned File Detection and Management
- Orphaned files are now automatically detected during every pull operation with clear warnings
- New
--delete-orphanedflag for automatic deletion, with optional--interactivemode for confirmation - Improved code organization and user experience with better error messages
Previous Release
This builds upon 3.2.0-SNAPSHOT which introduced comprehensive Git integration support.
Important Notes
- Always use dedicated directories for mirthsync operations
- Test thoroughly in development before production use
- Backup your data before using
--delete-orphaned
3.2.0-SNAPSHOT
Open Integration Engine (OIE) Support
- NEW: Full support for Open Integration Engine (OIE) 4.5.2
- Seamless compatibility with both traditional Mirth Connect and OIE instances
- OIE-specific configuration handling for naming conventions and download URLs
- Comprehensive test suite for OIE integration
- Special thanks to the Open Integration Engine project maintainers for keeping open-source Mirth alive!
Native Git Integration (Experimental)
- NEW: Comprehensive built-in git operations without requiring server credentials
- Available Commands:
init,status,add,commit,diff,log,branch,checkout,remote,pull,push,reset - Advanced Diff Support: Compare working directory, staged changes, and between commits/branches
- Git Reset Capabilities: Soft, mixed, and hard reset options with commit targeting
- Auto-Commit Integration: Automatically commit changes after pull/push operations
- Custom Author Support: Specify git author name and email for commits
- Experimental Notice: This feature requires extensive testing - use alongside traditional git workflows
3.1.0
-
NOTE that this version respects the --include-configuration-map
(false by default) parameter during both a "push" and a
"pull". Previous versions would always "pull" the
configuration map even if the parameter was not set or was
false. If you want to include the configuration map now
during a "pull" please ensure that you set the flag. -
New "--skip-disabled" flag to indicate whether the item (only
channels currently) being pushed or pulled should be included based
on its status. The flag defaults to 'false' and all items are pushed
or pulled no matter what the 'enabled' setting is. NOTE - this
feature only works on mirth versions >= 3.9. -
New "--disk-mode" setting that alters behavior around how granular
the resulting files are in the target directory.- Mode "backup" pushes and pulls a full backup XML file and doesn't
produce any other disk artifacts. - Mode "groups" pushes and pulls code at the next most granular level
which means that channel groups and code template library XML
actually contains the assocated channels and javascript - Mode "items" extracts code templates and channels from the respective
library or group XML. - Mode "code" extracts even further pulling all code from XML files
into individual language specific files.
- Mode "backup" pushes and pulls a full backup XML file and doesn't
3.0.4-SNAPSHOT
New -d --disk-mode flag for specifying depth which allows for different on-disk storage formats.
NOTE - this release is not ready for general use. Feel free to test and give feedback on the new feature on issue #34
3.0.3-SNAPSHOT
- New "--skip-disabled" flag to indicate whether the item (only
channels currently) being pushed or pulled should be included based
on its status. The flag defaults to 'false' and all items are pushed
or pulled no matter what the 'enabled' setting is. NOTE - this
feature only works on mirth versions >= 3.9.
3.0.2
- Support for getting the password from the MIRTHSYNC_PASSWORD
environment variable if --password is not specified - Prompt for password on console if no password is set, the console is
available and the interactive "-I" flag is set - Fix bug preventing local modifications from being pushed even with
--force flag specified