@einsia/agent-git 0.2.1 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +36 -0
  2. package/README.md +9 -10
  3. package/package.json +6 -6
package/CHANGELOG.md CHANGED
@@ -6,6 +6,42 @@ Every notable change to agit, the AgentGit CLI, by release. The format follows
6
6
  its [GitHub Release](https://github.com/Einsia/agent-git/releases), and the
7
7
  `@einsia/agent-git` npm package ships this file.
8
8
 
9
+ ## [0.2.2] - 2026-09-19
10
+
11
+ ### Added
12
+
13
+ - **Shared workspace controllers.** Accept project- and session-scoped authority
14
+ from the Hub controller, so collaborators can operate a shared session without
15
+ separate device grants. This requires a Hub with shared controller support;
16
+ personal peer/Cloud connections retain their existing protocol.
17
+ - Expose native model and reasoning-effort controls through peer remote control.
18
+ - Protect detected secrets automatically with reversible, repository-local
19
+ placeholders before saving or publishing session content.
20
+
21
+ ### Changed
22
+
23
+ - Keep native controls responsive while prepared settlement completes, reuse
24
+ healthy session worktrees and Hub connections, and replace repeated Git child
25
+ processes with bounded local object reads.
26
+ - Start tunnel transport independently of repository storage and overlap Cloud
27
+ admission and peer setup to reduce connection overhead.
28
+ - Official Hub usage requires usage statistics; installation attempts and stages
29
+ are included in the documented collection policy. Other Hubs retain their
30
+ opt-out controls. See [usage statistics](docs/telemetry.md).
31
+
32
+ ### Fixed
33
+
34
+ - Keep shared native subscriptions attached to controller authority, isolate each
35
+ viewer's replay, and suppress duplicate events on Cloud utility routes.
36
+ - Preserve early session events, uncertain command receipt identities, native
37
+ titles, and saved session identities outside the active catalog.
38
+ - Correct Windows path component handling and directory navigation.
39
+ - Distinguish stale daemon records from reused process IDs, recover stopped
40
+ daemons after upgrades, and enforce private state permissions under permissive
41
+ umasks.
42
+ - Preserve fresh native history during model reads and settlement without
43
+ blocking read-only controls on repository metadata work.
44
+
9
45
  ## [0.2.1] - 2026-09-17
10
46
 
11
47
  ### Added
package/README.md CHANGED
@@ -163,16 +163,15 @@ The section becomes the GitHub Release body (`scripts/release-notes.mjs` extract
163
163
  `release.yml`, with repository-relative links pinned to the release tag) and ships inside
164
164
  the `@einsia/agent-git` package.
165
165
 
166
- After the source release commit passes CI and is synchronized to GitHub `main`,
167
- verify the mirrored files and create the tag in that GitHub checkout. The mirror
168
- rewrites commit IDs, so the source repository's SHA is not the release SHA.
169
- Pushing the tag to GitHub runs the whole chain binaries first, npm right after:
170
-
171
- ```sh
172
- # Run from the verified Einsia/agent-git GitHub mirror checkout.
173
- git tag agit-v0.1.0
174
- git push git@github.com:Einsia/agent-git.git refs/tags/agit-v0.1.0
175
- ```
166
+ After the source release commit passes CI, merge it into GitLab `main`. Wait for
167
+ that pipeline's development builds and `mirror:github`, then run its manual
168
+ `release:github-tag` job. CI verifies the recorded source-to-mirror mapping and
169
+ creates `agit-v<version>` on the public mirror commit. Release tags are immutable;
170
+ a stale pipeline cannot publish after either `main` moves.
171
+
172
+ The mirror rewrites commit IDs, so the source SHA is not the release SHA. Do not
173
+ push release tags directly to GitHub. The CI-created tag starts the GitHub Release
174
+ workflow, which builds the binaries and then triggers npm publication.
176
175
 
177
176
  Distribution to users runs through the npm registry: each target ships as a
178
177
  platform sub-package (`@einsia/agent-git-linux-x64` and friends, gated by
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@einsia/agent-git",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
4
  "description": "Version control for agent sessions — the agit CLI plus skills/hooks/MCP wiring for Claude Code, Codex, OpenCode and Cursor. The AgentGit hub deploys separately.",
5
5
  "keywords": [
6
6
  "agit",
@@ -49,10 +49,10 @@
49
49
  "access": "public"
50
50
  },
51
51
  "optionalDependencies": {
52
- "@einsia/agent-git-linux-x64": "0.2.1",
53
- "@einsia/agent-git-linux-arm64": "0.2.1",
54
- "@einsia/agent-git-darwin-x64": "0.2.1",
55
- "@einsia/agent-git-darwin-arm64": "0.2.1",
56
- "@einsia/agent-git-win32-x64": "0.2.1"
52
+ "@einsia/agent-git-linux-x64": "0.2.2",
53
+ "@einsia/agent-git-linux-arm64": "0.2.2",
54
+ "@einsia/agent-git-darwin-x64": "0.2.2",
55
+ "@einsia/agent-git-darwin-arm64": "0.2.2",
56
+ "@einsia/agent-git-win32-x64": "0.2.2"
57
57
  }
58
58
  }