You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ac6396c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .config/repo/lockstep.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@
101
101
"honors a custom stdio",
102
102
"merges options.env"
103
103
],
104
-
"notes": "The patch adapter resolves and executes socket-patch with argument, environment, and stdio forwarding. The sparse upstream contains core implementation, CLI commands, and behavioral tests for incorporation. This row covers the execution adapter; patch algorithms are implemented by the upstream executable."
104
+
"notes": "The adapter resolves and executes `socket-patch` with argument, environment, and stdio forwarding. It remains the CLI implementation until the in-process TypeScript port reaches the upstream contract. The public SocketDev/socket-patch source pin is `15a6ba6f416c244e918ff01260a1bc91f67bc945` on `main`, with a depth-one single-branch checkout of core, CLI, and tests. The upstream license is MIT."
Copy file name to clipboardExpand all lines: AGENTS.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,3 +169,11 @@
169
169
- A written mermaid fence gets rewritten GitHub-safe at edit time. [`hook-registry`](docs/fleet/agents.md/hook-registry.md)
170
170
171
171
<!-- </fleet> -->
172
+
173
+
## 🏗️ CLI-Specific
174
+
175
+
- Build production native binaries with `pnpm run build:native:prod`; inspect them with `pnpm run check:native-package`.
176
+
- Use `pnpm test <path>` for focused tests. Native release tests live under `test/repo/unit/build/sea/` and `test/repo/unit/sea/`.
177
+
- Version selection, reservation, and source tagging belong to the npm release pipeline. Use the `next` dist-tag for prereleases; do not edit the package version to start a release.
178
+
- Native release signing and notarization run in macOS CI. The Apple certificate passphrase is CI-only. The workflow qualifies one packed artifact on all eight supported targets. See [native release](docs/repo/agents.md/native-release.md).
179
+
- Inspect staged package state with `pnpm run npm:staged`. After validation, approve eligible stages with `pnpm stage approve`; use the AI Drive/browser path only for CLI fallback or an npm challenge.
The npm release pipeline owns the release version, changelog, source commit, and reserved tag. Start it through `pnpm run publish:npm --dist-tag next` for the prerelease channel. Do not edit `package.json` to reserve a release. The native workflow consumes the reserved source SHA and package version.
4
+
5
+
## Local checks
6
+
7
+
Build the production native matrix and inspect the resulting package:
8
+
9
+
```sh
10
+
pnpm run build:native:prod
11
+
pnpm run check:native-package
12
+
```
13
+
14
+
Focused release tests:
15
+
16
+
```sh
17
+
pnpm test test/repo/unit/build/sea/release.test.mts
18
+
pnpm test test/repo/unit/check/publish-contract-is-valid.test.mts
19
+
pnpm test test/repo/unit/sea/check.test.mts
20
+
```
21
+
22
+
## CI qualification
23
+
24
+
The `publish: native` workflow builds and signs the package on macOS. The Apple certificate passphrase is supplied only as a CI secret. The workflow uploads one package archive, verifier, and receipt. Qualification jobs check the archive and digests, then run that verifier for all eight targets:
25
+
26
+
-`darwin-arm64`
27
+
-`darwin-x64`
28
+
-`linux-arm64`
29
+
-`linux-arm64-musl`
30
+
-`linux-x64`
31
+
-`linux-x64-musl`
32
+
-`win32-arm64`
33
+
-`win32-x64`
34
+
35
+
The macOS jobs also run Gatekeeper qualification. Treat the artifact as qualified only when the workflow reports success for every target.
36
+
37
+
## Stage
38
+
39
+
Inspect the staged package with `pnpm run npm:staged`. After artifact validation and the configured malware scan pass, approve eligible stages with `pnpm stage approve`. Ignore and monitor findings do not block approval. Use the AI Driver/browser fallback when the CLI cannot complete authentication or npm presents a challenge.
0 commit comments