Release
v2.5.2
clear-traceHotfix: Argus now records selected package-version sources in diagnostics, keeps CI logs concise, and reuses aggregate remediation MRs across failed retries.
Highlights
- 01
Selected versions are traceable
Fix-version and complication companion resolution now record what version Argus selected and which configured registry or source supplied it in the diagnostics file.
Read the guide → - 02
Retries reuse the same remediation MR
Aggregate remediation fingerprints now describe the underlying remediation plans rather than transient generated artifact keys, so retries update the existing Argus MR instead of opening duplicates after a failed run.
Read the guide →
Full notes
Added
- One customer-safe diagnostic prompt for RCA collection. The prompt helps customers analyse Argus failures, complications, package-version resolution, Maven errors, and branch-cleanup signals while redacting internal coordinates, registry URLs, paths, tokens, branch names, MR identifiers, and raw logs.
Changed
- Detailed registry version-discovery logs now go to the diagnostics file instead of the main CI job stream, keeping job output concise while preserving support evidence.
- Generated BUMP and OVERRIDE POM comments keep the machine-readable PATCH marker needed for stale cleanup, but use shorter human-readable text such as artifact -> version.
Fixed
- Failed retry runs no longer create duplicate aggregate Argus MRs for the same remediation bundle. Aggregate/final-pass MR fingerprints now ignore generated wrapper keys and use the underlying remediation plans.
- Fix-version and complication companion resolution now record the selected version and source registry in the diagnostics file (anchor.log or ARGUS_ANCHOR_LOG), including cached lookups, instead of going silent.