Skip to content

Changelog

Jump to bottom
Paul Rigor edited this page Jun 25, 2026 · 1 revision

Changelog

All notable changes to ADEPT are documented here. This project uses CalVer with the format MAJOR.MINOR.YYYYMMDD.

Overview

Each release is gated by an ASOPB (Agentic Security & Operations Performance Benchmark) scan that must achieve an ASPI score of 90 or higher before publication.

Latest Release

v1.0.20260622-rc1

Release Date: 2026-06-22

First public release candidate published to pnnl/adept-agentic.

Highlights

  • Slurm HPC Integration: v1 single-agent and v2 multi-agent with LLM-as-judge, COBRApy/Gurobi FBA validation
  • deploy-stack-v2: 6-phase deployment pipeline with control-plane health checks and observability
  • ASPI 94.2: 7-pass security scanner with institutional allowlist
  • IDE Integration: VS Code MCP connector, 5 custom Claude Code subagents, 29 skills
  • Security: nsjail implementation, network isolation, HMAC-SHA256 presigned URLs

v1.0.20260529

Release Date: 2026-05-29

Highlights

  • ASOPB Benchmark: Full 7-pass security and quality scanning pipeline with ASPI scoring
  • Multi-agent orchestration: Router and graph execution modes with RolePersona support
  • A2A federation: Agent-to-Agent communication between ADEPT instances via Gateway Registry
  • adept-connectors: Claude Desktop connector with MCP bridge and STDIO transport
  • 28+ scientific tools: BLAST, UniProt, PubChem, AlphaFold, ChromaDB RAG, sandbox execution
  • Response API: Primary API with full SSE streaming
  • Context management: Automatic compaction with token-aware truncation
  • YAML model catalog: Declarative LLM purpose routing without code changes
  • Three-tier network architecture: Frontend, application, and data network isolation
  • File-based secrets: Production-ready credential management with fallback chain

Version Scheme

ADEPT uses CalVer: MAJOR.MINOR.YYYYMMDD

  • MAJOR: Breaking changes to public APIs or architecture
  • MINOR: New features or significant enhancements
  • YYYYMMDD: Release date stamp

Both packages share the same version number, bumped simultaneously during the release process.

Release Process

  1. Version bump in both packages
  2. Squash-merge to main
  3. Git tag v<version>
  4. Stage release tree (make stage)
  5. ASOPB scan (ASPI >= 95 gate)
  6. Dry-run validation
  7. Manual publish (never automated)
  8. Tag released-<version>
  9. GitHub Release with notes

Home

Getting Started

Architecture

Deployment

User Guides

Developer Tools

CI/CD

Testing

Contributing

Reference

Clone this wiki locally