Skip to content

AIContext v0.4.0

Pre-release
Pre-release

Choose a tag to compare

View all tags
@mortylen mortylen released this 04 Nov 13:12
· 68 commits to main since this release
v0.4.0
43170b2

AIContext 0.4.0

AIContext 0.4.0 makes the CLI easier to start with and to run day to day: --version, an extended init profile, and export that honors exports.defaultTarget. The standalone binaries are also about three times smaller.

Highlights

  • aicontext --version (also -v and version) prints the tool version and the specification version.
  • aicontext init --profile extended creates starter architecture.md, decisions.md and constraints.md next to README.md and context.json, so a new project passes validate --strict as the Extended profile right away. The default stays core.
  • export without --target. When exports.defaultTarget is set in context.json, aicontext export uses it. --target always takes precedence, all means the targets from exports.targets, and if neither is available the command fails with a message that names both options.
  • Smaller standalone binaries. Self-contained, single-file binaries are now published with partial trimming: about 11 MB instead of about 36 MB for Windows x64. No .NET installation is required.

New

  • aicontext --version, -v, version.
  • aicontext init --profile <core|extended>.
  • export falls back to exports.defaultTarget and prints Using exports.defaultTarget '<value>' from .aicontext/context.json.
  • ProjectInitializer in the AIContext library (the init logic moved out of the CLI).
  • Release smoke test for the standalone binaries now also covers --version, the extended profile and rejection of an invalid context.json.
  • English user manual on the website.

Changed

  • init checks all files it would create before writing anything: if any of them exists it reports every conflict and writes nothing (unless --force). Files are now written with LF line endings and without a BOM.
  • SPEC 6.1 now defines the meaning of exports.defaultTarget. The schema and specVersion (0.1.0) are unchanged, so existing context.json files stay valid.

Upgrade notes

dotnet tool update --global AIContext.CLI
aicontext --version
  • Nothing breaks: export without --target used to fail, so existing scripts are unaffected. If your context.json already contains exports.defaultTarget, aicontext export now acts on it.
  • In CI you can keep using aicontext export --target all --check.

Known limitations

  • Partial trimming was verified locally on Windows x64; the other platforms are verified by the release workflow.
  • Secret detection is heuristic and does not replace a dedicated secret scanner.
  • Per-tool rule formats were verified against vendor documentation, not yet against every tool in real projects.
Assets 8
Loading