Skip to content

Commit 005cf0d

Browse files
committed
chore: ignore leaked dirfd capability probes
detectArtifactIoMode creates a .dirfd-probe-<pid> file, renames it, and unlinks it to decide whether dirfd-relative IO works. A process that dies between the rename and the unlink leaves an empty .dirfd-probe-<pid>.ok behind, and they accumulate in whatever directory the check ran from -- 84 of them, dating back to Aug 10, were sitting untracked in the repository root. They are machine-local scratch that must never be committed, and while they are untracked they also block the release preflight, which requires a clean tree. Ignoring them fixes both without deleting anything the user owns. The leak itself is worth fixing at the source, but that is a separate change to src/lab/artifacts/secure-fs.ts and not part of this work. Also adds the release plan for 2.14.2.
1 parent 9ca4c39 commit 005cf0d

2 files changed

Lines changed: 51 additions & 0 deletions

File tree

‎.gitignore‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,13 @@ devlog/**/security-advisory-draft*
3030
.tmp/
3131
.opencode/
3232

33+
# Capability probes from the trusted-artifact directory check
34+
# (src/lab/artifacts/secure-fs.ts detectArtifactIoMode). The probe is normally
35+
# unlinked immediately, but a process that dies between rename and unlink leaves
36+
# an empty file behind, and they accumulate in whatever directory the check ran
37+
# from. They are machine-local scratch and must never be committed.
38+
.dirfd-probe-*
39+
3340
# Local agent/session artifacts
3441
# These are per-machine agent state (goalplans, ledgers, evidence scratch).
3542
# They are never part of the product and must not be committed, not even with
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# 070 Release 2.14.2
2+
3+
The goal's DONE criteria end with "the release completed". That is the one clause still
4+
open: `package.json` says 2.13.0, the newest tag is `v2.14.1`, and **68 commits sit on
5+
`origin/main` since that tag** — including the nine that fix this incident.
6+
7+
## Version
8+
9+
`2.14.2`. The shipped change is a defect fix on an existing surface: no new API, no
10+
behaviour a caller opts into, and `/api/usage` responses are byte-identical to a cold read
11+
in every truncation state (032). Patch is the honest level. `v2.14.2` is unused, so the
12+
NEEDS_HUMAN collision clause does not apply.
13+
14+
## Note on package.json
15+
16+
It reads 2.13.0 while the newest tag is v2.14.1, because the release workflow bumps the
17+
manifest in its own commit and `main` here has moved on since. `scripts/release.ts` takes
18+
the target version as an argument and writes it, so the stale manifest is an input to the
19+
release rather than something to hand-edit first.
20+
21+
## Procedure
22+
23+
`bun scripts/release.ts 2.14.2 --tag latest --publish`, which runs its own preflight
24+
(clean tree, dependency audit, typecheck, tests, privacy scan), bumps and commits the
25+
version, pushes, waits for Cross-platform CI, then dispatches and watches the Release
26+
workflow. Publishing is tokenless via Trusted Publishing (OIDC); there is no NPM_TOKEN to
27+
supply.
28+
29+
The script is the release authority per AGENTS.md. Do not hand-roll `npm publish`, and do
30+
not weaken its gates — a local full-suite hang is a local problem, not a reason to skip the
31+
preflight the script runs in CI.
32+
33+
## Acceptance
34+
35+
- `v2.14.2` tagged on the promoted `main` commit.
36+
- Release workflow green.
37+
- `npm view opencodex version` returns 2.14.2.
38+
39+
## Risk
40+
41+
The user authorized push, preview/main promotion and deploy for this work. Release is the
42+
last authorized step of that same instruction ("main preview 머지하고 배포해 반드시"), not
43+
an expansion of it. If CI or OIDC is unavailable, that is the goal's BLOCKED clause and the
44+
phase stops there rather than publishing by hand.

0 commit comments

Comments
 (0)