Skip to content

AdversaryGraph v6.0.0

Latest
Latest

Choose a tag to compare

View all tags
@anpa1200 anpa1200 released this 17 Jul 08:52
v6.0.0
9876238
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

AdversaryGraph v6.0.0 Release Notes

Release date: 2026-07-17

AdversaryGraph v6.0.0 is the operational-evidence and controlled self-hosted
production-readiness release. It packages the capabilities delivered through
v5.9.1 with a repeatable release gate, corrected history, current visual
evidence, local case studies, and explicit deployment acceptance criteria.

Added

  • scripts/release-readiness.sh with quick and full release gates covering
    metadata, patch hygiene, default and production Compose rendering, frontend
    lint/build/browser tests, backend lint/tests, and the security validation
    suite.
  • Reproducible Playwright screenshot capture using sanitized deterministic API
    fixtures, plus four current 1920x1200 evidence images.
  • A screenshot manifest recording capture method, scope, limitations, image
    dimensions, sizes, and checksums.
  • Three local case studies for report-to-detection review, asset exposure
    prioritization, and controlled Attack Simulation/SIEM validation.
  • A release-readiness guide with deployment go/no-go criteria, backup and
    rollback requirements, security boundaries, evidence requirements, and
    post-release verification.
  • A consolidated overview of all changes from v5.0.0 through v5.9.1.

Corrected and Changed

  • Corrected v5.1-v5.4 release notes to match the canonical changelog and
    repository history.
  • Replaced stale hard-coded sidebar version text with the version from the
    frontend package metadata.
  • Updated backend, frontend, Helm, README, roadmap, security policy, changelog,
    version matrix, reviewer guide, release process, and upgrade guidance for
    v6.0.0.
  • Defined the release claim as production-ready for a controlled self-hosted
    deployment that passes the documented operator gates. The project does not
    claim managed SaaS or default internet-facing multi-tenant readiness.

Validation

Run the full local release gate:

./scripts/release-readiness.sh --full

The GitHub release workflow independently repeats backend tests and frontend
lint/build/browser tests before publishing versioned container images and the
release notes.

Upgrade Notes

  1. Back up PostgreSQL and retain the generated checksum.
  2. Record the current version, container state, health response, and deployment
    configuration.
  3. Render the production Compose configuration before rebuilding.
  4. Deploy v6.0.0 and run ./scripts/selftest.sh plus the documented feature
    smoke checks.
  5. Roll back to the previous tag and restore the pre-upgrade backup if a release
    acceptance criterion fails.

AdversaryGraph still uses additive startup schema compatibility rather than a
formal Alembic migration chain. A verified backup is therefore mandatory for
production upgrades.

Safety and Deployment Boundary

  • Use TLS and named authenticated users for exposed deployments.
  • Keep PostgreSQL, Redis, malware analysis, and attack-lab services on private
    networks.
  • Use managed secrets, backups, retention, monitoring, and log review.
  • Treat AI output, generated detections, actor similarity, network
    fingerprints, and synthetic telemetry as analyst-assistance evidence.
  • Run Attack Simulation only against approved lab fixtures.
  • Do not treat the default Compose stack as a managed or multi-tenant SaaS.

See Release Readiness,
Validation and Limitations, and
Production Readiness.

Assets 2
Loading