Update GitHub actions

[pvdbosch]

In builds of rest-guide and the openapi-* projects, we have some deprecation warnings in the builds about

• https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/ => will be problem in Spring 2024
• https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

For rest-guide, I already updated two offending github actions to latest version (+ JDK 17):

    - uses: actions/checkout@v4
    - name: Set up Adopt OpenJDK 17
      uses: actions/setup-java@v4
      with:
        distribution: adopt
        java-version: '17'

The release actions (actions/create-release@v1 and actions/upload-release-asset@v1) have become unmaintained however, and should be replaced by alternatives.

Is there someone who wants to work on this?

[jpraet]

GitHub CLI comes preinstalled on all GitHub hosted runners. If that meets the requirements, that seems more future proof to me than searching for an alternative action that risks becoming unmaintained: https://cli.github.com/manual/gh_release_create

[jpraet]

Once the updated gh-actions release workflow of https://github.com/belgif/openapi-location/pull/9 has been validated, I will create PRs to apply the same changes to the other repos.

[jpraet]

We also have these workflow templates that I forgot about. It is also possible to define reusable workflows.

[pvdbosch]

@jpraet , I released belgif-openapi-location 1.2.0 with the new Github Actions without a problem. The artifacts still have to be indexed by Maven Central, but I verified staging.

[jpraet]

Do I copy the configuration over to the other belgif/openapi-* repos, or should I try a reusable workflow?

[pvdbosch]

Reusable workflow looks a bit easier to maintain in the long run; if it isn't too much work

[jpraet]

Reusable workflows created in this new workflows repo, and activated for all belgif/openapi-* repos.