Skip to content

Update reference-demo-content.version to 1.8.0#1036

Merged
jayasanka-sack merged 1 commit into
mainfrom
demo-content-1.8.0
Jun 4, 2026
Merged

Update reference-demo-content.version to 1.8.0#1036
jayasanka-sack merged 1 commit into
mainfrom
demo-content-1.8.0

Conversation

@wikumChamith

Copy link
Copy Markdown
Member

No description provided.

@jayasanka-sack

Copy link
Copy Markdown
Member

Curious, can't we use the release job to achieve this?

@wikumChamith

wikumChamith commented Jun 4, 2026

Copy link
Copy Markdown
Member Author

This content package still doesn't have a GHA for release.

@dkayiwa

dkayiwa commented Jun 4, 2026

Copy link
Copy Markdown
Member

This content package still doesn't have a GHA for release.

Is now the time to add it?

@jayasanka-sack
jayasanka-sack enabled auto-merge (squash) June 4, 2026 10:57
@wikumChamith

Copy link
Copy Markdown
Member Author

This content package still doesn't have a GHA for release.

Is now the time to add it?

We need to check if we can reuse our parent module release GHA for content packages as well.

@jayasanka-sack
jayasanka-sack merged commit 28d12ae into main Jun 4, 2026
7 of 8 checks passed
@jayasanka-sack
jayasanka-sack deleted the demo-content-1.8.0 branch June 4, 2026 11:04
@ibacher

ibacher commented Jun 4, 2026

Copy link
Copy Markdown
Member

We need to check if we can reuse our parent module release GHA for content packages as well.

It probably needs a Java version specified, but the GHA stuff is pretty generic as long as something uses the maven-releases-plugin for releases.

@jayasanka-sack

jayasanka-sack commented Jun 4, 2026 via email

Copy link
Copy Markdown
Member

@wikumChamith

Copy link
Copy Markdown
Member Author

We need to check if we can reuse our parent module release GHA for content packages as well.

It probably needs a Java version specified, but the GHA stuff is pretty generic as long as something uses the maven-releases-plugin for releases.

We can use the release GHA, but I don't think we'll be able to use the one for the build, as it looks for an omod file in some steps.

PR: openmrs/openmrs-content-referenceapplication-demo#75

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.

5 participants