Skip to content

Simon/ci/stage jvm android before publish wpb 22853#1875

Open
SimonThormeyer wants to merge 16 commits intomainfrom
simon/ci/stage-jvm-android-before-publish-WPB-22853
Open

Simon/ci/stage jvm android before publish wpb 22853#1875
SimonThormeyer wants to merge 16 commits intomainfrom
simon/ci/stage-jvm-android-before-publish-WPB-22853

Conversation

@SimonThormeyer
Copy link
Member

@SimonThormeyer SimonThormeyer commented Feb 19, 2026

What's new in this PR

PR Submission Checklist for internal contributors
  • The PR Title
    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@SimonThormeyer SimonThormeyer force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 30 times, most recently from 2eb56e1 to be9a42d Compare February 20, 2026 13:08
@SimonThormeyer SimonThormeyer force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 3 times, most recently from db676c7 to 9e429e0 Compare February 20, 2026 14:14
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 3 times, most recently from 6276b3b to e112816 Compare March 2, 2026 08:53
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch from e112816 to 2be9d55 Compare March 2, 2026 14:34
SimonThormeyer and others added 11 commits March 2, 2026 17:19
@SimonThormeyer @typfel
build(gradle/jvm): use gradle-nexus publish plugin
4849e65
@SimonThormeyer @typfel
ci(jvm): fix: more specific jvm bindings target path
3e34740
@SimonThormeyer @typfel
ci(jvm): stage before releasing
945a455
@SimonThormeyer @typfel
build(gradle/android): use gradle-nexus publish plugin
00c4953
@SimonThormeyer @typfel
ci(android): stage before releasing
d58f21d
@SimonThormeyer @typfel
ci: move prepare-publish into its own workflow
894917d 
GHA doesn't allow calling other workflows as job steps, they need to be
their own job. So we're factoring out the the entire prepare-publish job
into its own workflow  so that prepare-jvm and prepare-android can be
their own job.
@SimonThormeyer @typfel
refactor: naming inconsistencies in gradle properties
54f1c56
@typfel
build(gradle/kmp): use gradle-nexus publish plugin
c17d265
@typfel
chore: explictly set package group
07f0c53
@typfel
fix(build): update versions script doesn't support all legal characte…
e8d9681 
…rs for gradle & swift versions
@typfel
ci: stop uploading android and jvm artifacts to the release during pu…
560b8b0 
…blishing

Now that we use the staging area at sonatype there's no point in uploading them anymore.
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch from 2be9d55 to 560b8b0 Compare March 2, 2026 16:25
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch from 121ba32 to 0f454fa Compare March 3, 2026 14:41
@typfel typfel marked this pull request as ready for review March 4, 2026 09:07
@typfel typfel requested a review from a team March 4, 2026 09:07
coriolinus
coriolinus approved these changes Mar 5, 2026
View reviewed changes
Copy link
Contributor

@coriolinus coriolinus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a large-ish caveat here, in that I am flying blind when it comes to Gradle and the JVM ecosystem. I don't know what I'm talking about, there.

That said, aside from the one nit, I see nothing to complain about here. Looks plausible!

.github/workflows/prepare-publish.yml
@@ -0,0 +1,65 @@
name: prepare publish
Copy link
Contributor

@coriolinus coriolinus Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Name could be significantly more descriptive here. Maybe "prepare publish jvm" or "... sonatype" or something?

Copy link
Member Author

@SimonThormeyer SimonThormeyer Mar 5, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This workflow is supposed to contain prepare publish jobs for any platform, not just jvm. E.g., the verify-tag job is platform-independent. Potentially in the future, we might require additional prepare jobs for platforms other than jvm, which is why keeping the workflow name generic here makes sense imo.

The "prepare publish jvm" naming you suggest is pretty similar to what you get if you compose the workflow name "prepare publish" and the respective job name, "jvm".

Note, there's also an "android" job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coriolinus coriolinus coriolinus approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@SimonThormeyer @coriolinus @typfel