-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BAH-4149: Bump Bahmni Core version to 1.3.0-SNAPSHOT and FHIR2 version to 2.3.0-SNAPSHOT. #215
base: master
Are you sure you want to change the base?
Conversation
This is a follow-on PR based on the changes discussed (here)[https://bahmni.slack.com/archives/C03LWT96L/p1732540018086699].
@@ -50,7 +50,7 @@ | |||
<bahmniIEOmodVersion>1.4.0</bahmniIEOmodVersion> | |||
<appointmentsVersion>2.0.2</appointmentsVersion> | |||
<pacsQueryVersion>1.4.0</pacsQueryVersion> | |||
<fhir2ModuleVersion>2.1.0</fhir2ModuleVersion> | |||
<fhir2ModuleVersion>2.3.0-SNAPSHOT</fhir2ModuleVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ruhanga This bumps two versions, would be great if you can add on the description on what enhancement / breaking change we might have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ruhanga Can you please raise a JIRA ticket and associate with descriptions and associate the PR to the card
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ruhanga I can see that the build on the upstream for fhir2 module is failing. https://github.com/openmrs/openmrs-module-fhir2/actions/runs/12319449923. Hope that should be fixed for your changes to be published |
Good catch, thanks for the observations @mohan-13. Let me let the community know of the build failure so it can be resolved ASAP before you can merge. |
This is a follow-on PR based on the changes discussed here.
This PR will ensure the following upgrades: