Skip to content

RELEASE.md

Latest commit

 

History

History
38 lines (28 loc) · 994 Bytes

RELEASE.md

File metadata and controls

38 lines (28 loc) · 994 Bytes
Raw

Release Process

Use this checklist for reviewer-friendly AdversaryGraph releases.

Pre-Release

  • Update VERSION.
  • Update frontend/package.json and frontend/package-lock.json.
  • Update backend API version in backend/main.py.
  • Move CHANGELOG.md entries from unreleased work into a dated version.
  • Add docs/release-notes/vX.Y.Z.md.
  • Confirm sample outputs and demo dataset still match the documented workflow.
  • Confirm no secrets, private reports, credentials, or customer data are added.

Verification

cd backend
PYTHONPATH=. python -m pytest -q

cd ../frontend
npm ci
npm run build

Tag And Publish

  1. Commit the release changes.
  2. Create tag vX.Y.Z.
  3. Push main and the tag.
  4. Create a GitHub release using docs/release-notes/vX.Y.Z.md.
  5. Confirm the public hub and docs links still resolve.

Post-Release

  • Check GitHub Actions.
  • Check the live workspace and docs site.
  • Update external discovery material only after the tag exists.