Skip to content

Conversation

@Jmevorach
Copy link
Contributor

This PR updates OpenEMR to v7.0.4 (would recommend and would like to please request we do a release after the PR is merged to v2.0.0 as I don't think this release could be considered "compatible" with previous releases and thus has to be a "major" release rather than a "minor" one).

@jesdynf
Copy link
Contributor

jesdynf commented Nov 22, 2025

Why wouldn't it be compatible? Just for the version update, or for other reasons?

@Jmevorach
Copy link
Contributor Author

@jesdynf It’s purely because of the version update. Anyone adopting the version introduced by this PR would also need to move to the newer OpenEMR Docker image. I don’t expect this to create compatibility issues, but it felt like a large enough change that users should consciously opt into it — hence my suggestion for a major bump. Very open to discussing what release level you think makes the most sense.

@jesdynf
Copy link
Contributor

jesdynf commented Nov 22, 2025

@bradymiller What's the expectation for a patch? Is it okay to assume that somebody on 7.0.3 should go to 7.0.4, citing security issues or bugfixes, or is it that the version update is more explicitly opt-in and we shouldn't meddle?

@bradymiller
Copy link
Member

Ideally should go to 7.0.3 to 7.0.4 since 7.0.3 will no longer be supported with patches (ie. security fixes). And already have several that will be in 7.0.4 (and not 7.0.3). At end of day ,though, up to user.

@jesdynf jesdynf merged commit 4a35f68 into openemr:main Nov 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants