# git-cas v6.5.5 Release Notes

v6.5.5 makes every git-cas-owned Git commit independent of ambient user
configuration. Root-set, publication, and vault writes now work in a clean bare
repository without configuring a personal author or committer.

## Self-Contained Commit Identity

`GitRefAdapter.createCommit()` supplies this stable identity to each internal
`git commit-tree` operation:

```text
git-cas <git-cas@example.invalid>
```

The identity is scoped to the individual Git command. git-cas does not invoke
`git config`, mutate repository or global settings, or require applications to
provide personal identity.

This fixes storage writes performed against bare or automation-owned
repositories where `user.name` and `user.email` are deliberately absent. The
failure was exposed by a clean-Linux retained-substrate migration rehearsal:
post-promotion root-set retention reached `git commit-tree`, which otherwise
stopped with `Author identity unknown`.

## Verification

Unit coverage observes all four author and committer environment variables.
Real-Git integration reads a root-set commit through native Git and verifies
both headers exactly. The versioned release candidate passed the complete
Node, Bun, and Deno unit and integration matrix, public type compatibility,
examples, lint, build stamping, and package dry-runs.

## Compatibility

This release changes no public API or stored-data schema and requires no
migration. Existing refs, objects, handles, and retained generations remain
valid.

Git identity is part of commit bytes, so newly created internal commit OIDs may
differ from commits that previously inherited an operator identity. Internal
commit OIDs remain opaque generations; callers must not derive them in advance
or interpret personal attribution from them.