Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
25 lines
865 B
Plaintext
25 lines
865 B
Plaintext
Git v2.30.2 Release Notes
|
|
=========================
|
|
|
|
This release addresses the security issue CVE-2022-24765.
|
|
|
|
Fixes since v2.30.2
|
|
-------------------
|
|
|
|
* Build fix on Windows.
|
|
|
|
* Fix `GIT_CEILING_DIRECTORIES` with Windows-style root directories.
|
|
|
|
* CVE-2022-24765:
|
|
On multi-user machines, Git users might find themselves
|
|
unexpectedly in a Git worktree, e.g. when another user created a
|
|
repository in `C:\.git`, in a mounted network drive or in a
|
|
scratch space. Merely having a Git-aware prompt that runs `git
|
|
status` (or `git diff`) and navigating to a directory which is
|
|
supposedly not a Git worktree, or opening such a directory in an
|
|
editor or IDE such as VS Code or Atom, will potentially run
|
|
commands defined by that other user.
|
|
|
|
Credit for finding this vulnerability goes to 俞晨东; The fix was
|
|
authored by Johannes Schindelin.
|