v0.1.0
Release Process
This project is early research software. Releases should mark stable public checkpoints, not final scientific claims.
Before creating a release
- Make sure the working tree is clean.
git status --short --branch- Run local checks.
python scripts/dev.py check- Review generated and ignored files.
git status --ignored --shortConfirm that .env, API keys, private prompts, and unreviewed generated outputs are not being committed.
- Update
CHANGELOG.md.
Move unreleased notes into a versioned section such as:
## v0.1.0 - 2026-04-28- Commit and push all release documentation changes.
Creating v0.1.0 on GitHub
Because GitHub CLI may not be authenticated for repository management, the simplest path is the web UI:
- Open the repository on GitHub.
- Click Releases.
- Click Draft a new release.
- Choose Create a new tag and enter:
v0.1.0
- Target branch:
master
- Release title:
v0.1.0 - Public open-source baseline
- Release notes:
Initial public release of the AANA evaluation pipeline.
Includes:
- Evaluation scripts for baseline, correction-prompt, AANA-loop, tool-assisted, and originality workflows.
- Beginner-facing README and documentation.
- Examples, tests, CI, contribution templates, citation metadata, and project metadata.
- MIT license.
This is early research software. Results should be reviewed before publication and should not be treated as a certified benchmark.- Leave Set as a pre-release unchecked unless you want GitHub to mark the release as unstable.
- Click Publish release.
After release
- Confirm the release page links to the correct tag.
- Confirm the README badges still render.
- Confirm the Cite this repository button appears from
CITATION.cff. - Start the next changelog section for future changes.