Releases

ATAF does not maintain an in-repository changelog. All releases are published on GitHub and as artifacts on Maven Central.

• GitHub releases: github.com/it-at-m/agile-test-automation-framework/releases
• Maven Central: artifacts are published under the de.muenchen.ataf group.

The latest release tag is also shown next to the site title in the top navigation; it is fetched live from the GitHub Releases API.

Maven Central Artifacts

After each release, consumers (such as zmsautomation) can depend on:

<dependency>
    <groupId>de.muenchen.ataf</groupId>
    <artifactId>core</artifactId>
    <version>0.3.4</version>
</dependency>

<dependency>
    <groupId>de.muenchen.ataf</groupId>
    <artifactId>rest</artifactId>
    <version>0.3.4</version>
</dependency>

<dependency>
    <groupId>de.muenchen.ataf</groupId>
    <artifactId>web</artifactId>
    <version>0.3.4</version>
</dependency>

Pin to an explicit version (for example 0.3.4). Omitting the version tag will cause Maven to use the latest available version, which is not recommended.

Release Process

The repository is configured to publish ATAF artifacts to Maven Central using a GitHub Actions workflow:

• Workflow: .github/workflows/maven-release.yml
• Action: it-at-m/lhm_actions Maven release composite action

To create a release:

1. Open the Actions tab in GitHub and select Release Maven.
2. Use 0.3.4 as the releaseVersion (or a higher version for future releases).
3. Use 0.3.5-SNAPSHOT (or the next snapshot) as the developmentVersion.
4. Run the workflow. It will:
   • Use the Maven release profile (which skips tests during the release build).
   • Sign and deploy artifacts to Maven Central via the Sonatype Central publishing plugin.
   • Open a pull request with the updated snapshot version (when use-pr is enabled).