Argus
Release ledger

Release

v1.3.1

steady gaze

Patch release fixing the final-pass native-cleanup probe for projects that pass a relative settings.xml via --maven-args.

Download binary
Linux · amd64Linux · arm64macOS · arm64
Diagnostic skillCI/CD componentHow to use the skill →

Highlights

  • 01

    Relative settings.xml works in cleanup

    Teams passing -s build-config/maven-settings.xml via --maven-args no longer see the final remediation pass fail with 'user settings file does not exist'. The native-cleanup probe now runs from the project directory, matching every other Maven invocation.

    Read the guide →

Full notes

Changed

  • Updated the GitLab CI/CD component and documentation examples to default to Argus 1.3.1.

Fixed

  • Fixed the final remediation pass cleanup probe failing with maven execution exited with status 1: The specified user settings file does not exist on projects that pass a relative -s build-config/maven-settings.xml via --maven-args. The native-cleanup probe wrote its candidate POM under patches/ (matching the artifact under test), so Maven looked for the settings file relative to patches/ where it doesn't exist. The probe now anchors its candidate POM in the project directory — the same directory Maven was using for every other invocation.