Repository navigation
Bumped version to 4.7.0 - #487
Merged
Merged
Conversation
Pull in updates to get ready for 4.7.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Jon Bartels <jonathan.bartels@gmail.com>
jonbartels
requested review from
a team,
NicoPiel,
gibson9583,
kayyagari,
kpalang,
mgaffigan,
ssrowe and
tonygermano
October 14, 2026 15:50
mgaffigan
approved these changes
Oct 14, 2026
NicoPiel
approved these changes
Oct 14, 2026
tonygermano
approved these changes
Oct 14, 2026
tonygermano
left a comment
Member
There was a problem hiding this comment.
Approving, but next time let's skip the install4j file. That's a separate PR and this creates a merge conflict with the edits in progress.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull in updates to get ready for 4.7.0.
Follows #301 (the 4.6.0 bump), adapted to the post-Gradle-migration layout:
server/mirth-build.propertiesis gone, sogradle.propertiescarries the build version now, andserver/src/test/resources/mirth.propertiesis a new place the version appears.Changes
gradle.properties— build version4.6.0→4.7.0server/conf/mirth.properties,server/src/test/resources/mirth.properties— migration versionserver/dbconf/{derby,mysql,oracle,postgres,sqlserver}/*-database.sql—SCHEMA_INFOseed versiontools/install4j/oie-installer-config.install4j— installer<application version="...">server/src/com/mirth/connect/client/core/Version.java— appendedv4_7_0("4.7.0");v4_6_0stays as history sincegetLatest()returns the last constantserver/src/com/mirth/connect/server/migration/ServerMigrator.java—case v4_7_0: return null;No
Migrate4_7_0is added, matching how #301 handled 4.6.0 — 4.7.0 ships no schema change beyond theSCHEMA_INFOversion row. If a config/schema migration turns out to be needed, it belongs in its own PR.ci/tests/*/channels/*/channel.xmlfixtures are deliberately left atversion="4.6.0": they are channel exports, not version declarations, so leaving them keeps CI exercising the import/upgrade path from the prior release. #301 likewise did not touch fixtures.Verification
./gradlew :server:compileJava— passes./gradlew :server:test— 667 tests, 0 failures. This covers the bump-sensitive tests: those initializingObjectXMLSerializerfromVersion.getLatest()(ObjectXMLSerializerTest,ObjectJSONSerializerTest,MapUtilTest,HttpReceiverPropertiesTest,JsonMessageBodyReaderTest,ServerConfigurationRestorerTest) and the migration tests callingsetStartingVersion(Version.getLatest())(Migrate3_7_0Test,Migrate4_0_0Test,Migrate4_3_0Test).xmllint --noout tools/install4j/oie-installer-config.install4j— parsesgit grep '4\.6\.0' -- . ':!ci/tests'— only the retainedv4_6_0enum constant remains🤖 Generated with Claude Code