Strengthening the Release Process for Quarkiverse

[gastaldi]

Hello @quarkiverse/quarkiverse-members!

Due to https://quarkus.io/blog/quarkiverse-and-smallrye-new-release-process/, we have changed our release process internally. The organization's secrets were moved to the https://github.com/quarkiverse/quarkiverse-release repository, so the release.yml in your repository won't work anymore. The Maven central credentials were also rotated for extra security.

What do I need to do?

You'll find a PR titled Split and Reuse the Release workflow in your repository. If you haven't changed the original release workflow, merge it.

The workflow is merged. How do I trigger a new release?

As described in https://hub.quarkiverse.io/release/, the steps to perform a release haven't changed.

I need help migrating my release workflow

Ping us in this thread and we'll be glad to help you.

[melloware]

I would just like to say I LOVE the new release process if for nothing else than it publishes the release to GitHub Releases which I always was doing manually 😄

[metacosm]

Ah, nice! Haven't tried it yet but good to know!

[CodeSimcoe]

Hello @gastaldi
For extension quarkus-fx we need a DISPLAY to be present for tests, that's why build.yml makes use of xvfb :

      - name: Run Tests
        run: xvfb-run ./mvnw -B -ntp verify

Since the new release update, tests do fail on release

[INFO] 2024-10-18 06:43:54,153 ERROR [io.qua.fx.QuarkusFxApplication] (Thread-30) An exception occurred in Fx application launch: java.lang.UnsupportedOperationException: Unable to open DISPLAY

I bet release-perform.yml and release-prepare.yml shall be updated ?
Not really familiar with these pipelines, can you help ?

Also, currently the tests fails but the action doesn't until it times out.

Thanks

[gastaldi]

@CodeSimcoe I've created quarkiverse/quarkus-fx#91 using the prepare-release-headless.yml I introduced in the .github repository. Let me know if that works for you

[CodeSimcoe]

It fails for now

(java:1942): dbind-WARNING **: 13:35:29.745: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
2024-10-18 13:35:29,833 INFO  [io.quarkus] (main) quarkus-fx-deployment stopped in 0.005s
Error:  Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.362 s <<< FAILURE! -- in io.quarkiverse.fx.deployment.FxStartupTest

[gastaldi]

@CodeSimcoe I fixed the release by introducing a maven_executable input.

Release 0.8.0 worked as a charm: https://github.com/quarkiverse/quarkus-fx/releases/tag/0.8.0

[CodeSimcoe]

Thanks a lot @gastaldi !

[turing85]

Hi!
@gastaldi and I just found something.
The new release process auto-generates release notes. This new process does not honor SemVer. So for example, if we release a version 3.6.0 and a version 3.5.1 afterwards (which we just did in quarkus-artemis), the later but "smaller" version (i.e. 3.5.1) will be set as latest.

[gastaldi]

I created https://github.com/quarkiverse/quarkiverse-release/issues/7 to track this

[metacosm]

Another side-effect to this change: I have workflows that release snapshot versions of my extension. These do not work anymore because they were using the GPG key for artifact signing. Could we have such a snapshot release workflow in Quarkiverse, please?

[gastaldi]

Of course: here is an example: https://github.com/quarkiverse/quarkus-prettytime/blob/main/.github/workflows/deploy-snapshots.yml

It's also available when you create a new workflow here: https://github.com/quarkiverse/quarkus-operator-sdk/actions/new

[metacosm]

I assume that the snapshot deployment is only triggered if we set a version to something -SNAPSHOT?

[gastaldi]

Yes, that's correct, but the secret is in the ref parameter. In a normal deployment it would be the tag version

[metacosm]

Been having problems with this since today: the token creation has been failing, see for example: https://github.com/quarkiverse/quarkus-operator-sdk/actions/runs/11610645678/job/32330581819#step:13:15

[gastaldi]

Your workflow is missing secrets: inherit. Here is a PR fixing it: quarkiverse/quarkus-operator-sdk#989

[metacosm]

It would also be useful to be able to pass maven arguments to the release process so that people can activate profiles, set properties, etc.

[gastaldi]

PRs are welcome 😉