Skip to content

AOCI-CODE v0.1.0-rc19

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Oct 08:05
· 8 commits to main since this release

AOCI-CODE v0.1.0-rc19 is built from 0864b1aaed840c4ef15fb4f8bb365099ef578ce4.

Two fixes from user reports: Scope Change replay, and directory names that
hid source from the index.

  • Scope Change replay no longer depends on files other tools write (#101).
    A Git-ignored path that no rule governs and that the active Baseline does
    not hold leaves the transaction envelope, and the candidate count and
    selection identity the envelope carries are recomputed from the paths kept,
    so a lock or cache file appearing between scope preview and scope apply
    (CodeGraph's watcher, for one) no longer ends in deterministic_replay_failed
    or managed_scope_replay_mismatch. A preview minted by rc18 or older fails
    replay once after the upgrade; run scope preview again. .codegraph is a
    built-in runtime directory like .aoci. Found and diagnosed by @Zedthm and
    @mahirhir.
  • Directory names that can denote source are no longer a built-in safety rule
    (#100). Through rc18 backup, backups, build, cache, coverage,
    dist, target, temp, tmp, uploads, artifacts, and vendor were
    matched against every path component and hard excluded with no way back:
    src/backup, views/monitor/cache, and tests/api/coverage were dropped
    from the index silently. The built-in rule now keeps only names that never
    denote source (node_modules, __pycache__, .next, .nuxt, .output,
    .cache, the third-party distribution names); the rest are governed by
    exclude_dirs, which init already writes into .aoci/config.json, so an
    existing repository changes no role on upgrade and now has a door: remove
    the name with aoci config set exclude_dirs ... and run
    aoci scope activate. scope explain reports a configured exclusion as
    exclude_dirs:<name> or exclude_files:<pattern> instead of
    project_config. Two names were never in the default list: a tracked module
    under a nested cache/ or temp/ becomes a Missing Entry after the upgrade
    and is authored like any new source; a git-ignored one stays excluded but is
    listed per file rather than collapsed unless exclude_dirs names it.
  • Black-box: a scenario plants a file in a git-ignored directory between
    preview and apply; the upgrade-axis fixture carries a tracked module named
    backup that every release must keep out across the upgrade.
  • Dependencies: golang.org/x/text 0.41.0 (GO-2026-6629, a panic on crafted
    input in x/text/secure/precis, reachable through the database drivers'
    SASL preparation) and golang.org/x/sync 0.22.0 with it.

See docs/install.md and docs/supply-chain.md for asset verification.